AWS social-messaging documentation change
Summary
Simplified explanation of default permissions by removing explicit references to AWS Management Console, CLI, and API access restrictions
Security assessment
The change removes specific examples of access methods (Console/CLI/API) but maintains the core security concept of default deny and IAM policy requirements. This appears to be a documentation simplification rather than addressing a specific vulnerability or security feature update.
Diff
diff --git a/social-messaging/latest/userguide/security_iam_id-based-policy-examples.md b/social-messaging/latest/userguide/security_iam_id-based-policy-examples.md index febaca7e1..29660e074 100644 --- a//social-messaging/latest/userguide/security_iam_id-based-policy-examples.md +++ b//social-messaging/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify AWS End User Messaging Social 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 Social resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.