AWS connect documentation change
Summary
Updated 'AWS CloudFormation' to 'CloudFormation' for consistency. No functional changes to IAM policy guidance.
Security assessment
The change is purely a naming convention adjustment. Existing security guidance (e.g., SSL requirements) remains unchanged.
Diff
diff --git a/connect/latest/adminguide/security_iam_id-based-policy-examples.md b/connect/latest/adminguide/security_iam_id-based-policy-examples.md index 6230c5ea8..683293def 100644 --- a//connect/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//connect/latest/adminguide/security_iam_id-based-policy-examples.md @@ -44 +44 @@ 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_.