AWS acm documentation change
Summary
Removed mention of users being unable to perform tasks via AWS Management Console, CLI, or API by default. Simplified explanation of default permissions and IAM policy creation process.
Security assessment
The change removes redundant information about default access restrictions (standard IAM behavior) but does not address a specific security vulnerability or weakness. It focuses on simplifying policy documentation rather than introducing or modifying security controls.
Diff
diff --git a/acm/latest/userguide/security_iam_id-based-policy-examples.md b/acm/latest/userguide/security_iam_id-based-policy-examples.md index 547286e29..5d05c6e5f 100644 --- a//acm/latest/userguide/security_iam_id-based-policy-examples.md +++ b//acm/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsL -By default, users and roles don't have permission to create or modify ACM 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 ACM resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.