AWS r53recovery documentation change
Summary
Condensed IAM policy guidance by eliminating access method restrictions explanation
Security assessment
Simplifies documentation flow without changing security posture. Maintains core security principle of requiring explicit IAM policies for resource access.
Diff
diff --git a/r53recovery/latest/dg/security_iam_id-based-policy-examples-zonalautoshift.md b/r53recovery/latest/dg/security_iam_id-based-policy-examples-zonalautoshift.md index 348e3abc5..2d0c9bea0 100644 --- a//r53recovery/latest/dg/security_iam_id-based-policy-examples-zonalautoshift.md +++ b//r53recovery/latest/dg/security_iam_id-based-policy-examples-zonalautoshift.md @@ -9 +9 @@ Policy best practicesExample: Console accessExamples: 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.