AWS outposts documentation change
Summary
Simplified default permissions description by removing references to console/CLI/API access restrictions
Security assessment
Change appears to be editorial simplification rather than security-related. The core message about default deny policies remains intact, with no evidence of addressing or introducing security flaws.
Diff
diff --git a/outposts/latest/userguide/security_iam_id-based-policy-examples.md b/outposts/latest/userguide/security_iam_id-based-policy-examples.md index 8ad7b81ab..710b6c726 100644 --- a//outposts/latest/userguide/security_iam_id-based-policy-examples.md +++ b//outposts/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesExample: Using resource-level permissions -By default, users and roles don't have permission to create or modify AWS Outposts 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 Outposts resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.