AWS m2 documentation change
Summary
Removed mention of users not being able to perform tasks via AWS Management Console, CLI, or API by default. Simplified the explanation of default permissions.
Security assessment
The change removes redundant information about default access restrictions but does not address any specific security vulnerability or weakness. It appears to be a documentation simplification rather than a security-related update.
Diff
diff --git a/m2/latest/userguide/security_iam_id-based-policy-examples.md b/m2/latest/userguide/security_iam_id-based-policy-examples.md index 8e67fd8e5..30756a12f 100644 --- a//m2/latest/userguide/security_iam_id-based-policy-examples.md +++ b//m2/latest/userguide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) wil -By default, users and roles don't have permission to create or modify AWS Mainframe Modernization 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 Mainframe Modernization resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.