AWS rolesanywhere documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in IAM policy condition example
Security assessment
The change is a terminology update aligning with branding conventions. The security guidance about using policy conditions (including SSL requirements) remains unchanged. No specific security vulnerability or new security feature documentation was added.
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 1842ded9c..60c82a190 100644 --- a//rolesanywhere/latest/userguide/security_iam_id-based-policy-examples.md +++ b//rolesanywhere/latest/userguide/security_iam_id-based-policy-examples.md @@ -34 +34 @@ Identity-based policies determine whether someone can create, access, or delete - * **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as AWS CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the _IAM User Guide_. + * **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the _IAM User Guide_.