AWS push-notifications documentation change
Summary
Simplified explanation of default permissions by removing specific interface examples (Console/CLI/API)
Security assessment
The change removes explicit mention of access denial through AWS Management Console, CLI, and API interfaces but maintains the core security concept of default deny. This appears to be a documentation clarification rather than addressing a specific security vulnerability or weakness.
Diff
diff --git a/push-notifications/latest/userguide/security_iam_id-based-policy-examples.md b/push-notifications/latest/userguide/security_iam_id-based-policy-examples.md index e1b887b7b..da35ef35a 100644 --- a//push-notifications/latest/userguide/security_iam_id-based-policy-examples.md +++ b//push-notifications/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 Push 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 Push resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.