AWS one-enterprise documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API without permissions, simplifying the default security posture explanation
Security assessment
The change removes specific examples of access denial mechanisms but does not introduce new security controls or address a specific vulnerability. It appears to be a documentation simplification rather than a security-related update.
Diff
diff --git a/one-enterprise/latest/userguide/security_iam_id-based-policy-examples.md b/one-enterprise/latest/userguide/security_iam_id-based-policy-examples.md index fc8f5995f..e838db7d0 100644 --- a//one-enterprise/latest/userguide/security_iam_id-based-policy-examples.md +++ b//one-enterprise/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsR -By default, users and roles don't have permission to create or modify Amazon One Enterprise 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 Amazon One Enterprise resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.