AWS rolesanywhere documentation change
Summary
Removed explicit mention of AWS Management Console/CLI/API access limitations in default permissions explanation
Security assessment
Change simplifies documentation phrasing about default permissions but doesn't address a specific vulnerability or security incident. The modification removes redundant clarification about access methods (console/CLI/API) while maintaining the core security concept of least-privilege defaults.
Diff
diff --git a/rolesanywhere/latest/userguide/security_iam_id-based-policy-examples.md b/rolesanywhere/latest/userguide/security_iam_id-based-policy-examples.md index 15c1786cd..1842ded9c 100644 --- a//rolesanywhere/latest/userguide/security_iam_id-based-policy-examples.md +++ b//rolesanywhere/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 IAM Roles Anywhere 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 IAM Roles Anywhere resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.