AWS sms-voice documentation change
Summary
Simplified explanation of default permissions by removing redundant details about console/CLI/API access restrictions
Security assessment
The change removes explicit mention of access restrictions through specific interfaces (console/CLI/API) but maintains the core security principle of least privilege. This appears to be a documentation clarification rather than addressing a specific vulnerability.
Diff
diff --git a/sms-voice/latest/userguide/security_iam_id-based-policy-examples.md b/sms-voice/latest/userguide/security_iam_id-based-policy-examples.md index 8c085bb5e..b68444403 100644 --- a//sms-voice/latest/userguide/security_iam_id-based-policy-examples.md +++ b//sms-voice/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsE -By default, users and roles don't have permission to create or modify AWS End User Messaging SMS resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify AWS End User Messaging SMS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.