AWS organizations documentation change
Summary
Simplified language about default permissions by removing explicit mention of console/CLI/API access limitations
Security assessment
The change appears to be a documentation style improvement rather than addressing security flaws. The core message about default deny remains intact without introducing new security features or vulnerability fixes.
Diff
diff --git a/organizations/latest/userguide/security_iam_id-based-policy-examples.md b/organizations/latest/userguide/security_iam_id-based-policy-examples.md index 2dcf8b405..8e8eb7d50 100644 --- a//organizations/latest/userguide/security_iam_id-based-policy-examples.md +++ b//organizations/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsG -By default, users and roles don't have permission to create or modify Organizations 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 Organizations resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.