AWS r53recovery documentation change
Summary
Shortened IAM policy introduction by removing access method details and role assignment process
Security assessment
Documentation refinement without security impact. Preserves critical security concept of least privilege through IAM policies while removing implementation details.
Diff
diff --git a/r53recovery/latest/dg/security_iam_id-based-policy-examples-zonal.md b/r53recovery/latest/dg/security_iam_id-based-policy-examples-zonal.md index 558b0628a..df116fa26 100644 --- a//r53recovery/latest/dg/security_iam_id-based-policy-examples-zonal.md +++ b//r53recovery/latest/dg/security_iam_id-based-policy-examples-zonal.md @@ -9 +9 @@ Policy best practicesExample: Console accessExample: API actions -By default, users and roles don't have permission to create or modify ARC 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 ARC resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.