AWS r53recovery documentation change
Summary
Removed redundant information about access methods (Console/CLI/API) and role assumption process from IAM policy introduction
Security assessment
Change simplifies documentation without altering security meaning. Removes explanation about access methods being restricted by default, but maintains core IAM policy guidance. No evidence of addressing vulnerabilities.
Diff
diff --git a/r53recovery/latest/dg/security_iam_id-based-policy-examples-readiness.md b/r53recovery/latest/dg/security_iam_id-based-policy-examples-readiness.md index 8032fba9d..a7c9e3ee9 100644 --- a//r53recovery/latest/dg/security_iam_id-based-policy-examples-readiness.md +++ b//r53recovery/latest/dg/security_iam_id-based-policy-examples-readiness.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.