AWS pcs documentation change
Summary
Simplified default permissions explanation by removing redundant details about console/CLI/API access
Security assessment
This is a editorial change that removes redundant information about default lack of access through various interfaces. No security-related content was added or modified beyond basic policy documentation improvements.
Diff
diff --git a/pcs/latest/userguide/security_iam_id-based-policy-examples.md b/pcs/latest/userguide/security_iam_id-based-policy-examples.md index c601d0ea8..6615a9b45 100644 --- a//pcs/latest/userguide/security_iam_id-based-policy-examples.md +++ b//pcs/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify AWS PCS 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 PCS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.