AWS amplify documentation change
Summary
Updated documentation to replace 'AWS CloudFormation' with 'CloudFormation' for consistency in naming
Security assessment
The change is a minor editorial adjustment to service naming conventions. The security-related content about using IAM policy conditions (e.g., requiring SSL) remains unchanged and was not enhanced or modified in a security context.
Diff
diff --git a/amplify/latest/userguide/security_iam_id-based-policy-examples.md b/amplify/latest/userguide/security_iam_id-based-policy-examples.md index bf1dfb2f4..121c12ad3 100644 --- a//amplify/latest/userguide/security_iam_id-based-policy-examples.md +++ b//amplify/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_.