AWS outposts documentation change
Summary
Simplified explanation of default permissions and policy creation process
Security assessment
Removes clarification about default denial of console/CLI/API access but doesn't alter security controls. Change is editorial rather than security-related.
Diff
diff --git a/outposts/latest/network-userguide/security_iam_id-based-policy-examples.md b/outposts/latest/network-userguide/security_iam_id-based-policy-examples.md index 5ac997a21..8c9a663b8 100644 --- a//outposts/latest/network-userguide/security_iam_id-based-policy-examples.md +++ b//outposts/latest/network-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.