AWS outposts documentation change
Summary
Simplified default permissions statement by removing references to AWS Management Console, CLI, and API access restrictions
Security assessment
The change clarifies default permissions but does not introduce or resolve security controls. Removing interface-specific restrictions is a documentation refinement without evidence of security impact.
Diff
diff --git a/outposts/latest/server-userguide/security_iam_id-based-policy-examples.md b/outposts/latest/server-userguide/security_iam_id-based-policy-examples.md index 46d9a490b..5dbf80fe2 100644 --- a//outposts/latest/server-userguide/security_iam_id-based-policy-examples.md +++ b//outposts/latest/server-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.