AWS verified-access documentation change
Summary
Updated IAM policy example documentation to use 'CloudFormation' instead of 'AWS CloudFormation' in a service reference
Security assessment
This is a consistent branding/naming update across documentation (same as the Translate example). No security implications are present as the change only standardizes service naming without altering policy logic or security recommendations.
Diff
diff --git a/verified-access/latest/ug/security_iam_id-based-policy-examples.md b/verified-access/latest/ug/security_iam_id-based-policy-examples.md index 01606fb7e..bf886f0c3 100644 --- a//verified-access/latest/ug/security_iam_id-based-policy-examples.md +++ b//verified-access/latest/ug/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_.