AWS mpa documentation change
Summary
Simplified explanation of default permissions by removing explicit references to AWS Management Console/CLI/API limitations
Security assessment
The change removes specific examples of access methods (Console/CLI/API) from the default permissions description but maintains the core security principle of least privilege. This is a documentation clarification rather than a response to a security vulnerability or addition of security controls.
Diff
diff --git a/mpa/latest/userguide/security_iam_id-based-policy-examples.md b/mpa/latest/userguide/security_iam_id-based-policy-examples.md index 2ffe8e235..d16078454 100644 --- a//mpa/latest/userguide/security_iam_id-based-policy-examples.md +++ b//mpa/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsC -By default, users and roles don't have permission to create or modify Multi-party approval 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 Multi-party approval resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.