AWS config documentation change
Summary
Updated documentation example to use 'CloudFormation' instead of 'AWS CloudFormation' in IAM policy condition context
Security assessment
This is a minor terminology change without altering security meaning or functionality. The update appears to be stylistic/naming consistency rather than addressing security concerns or adding security guidance.
Diff
diff --git a/config/latest/developerguide/security_iam_id-based-policy-examples.md b/config/latest/developerguide/security_iam_id-based-policy-examples.md index c060085d8..14b207b8c 100644 --- a//config/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//config/latest/developerguide/security_iam_id-based-policy-examples.md @@ -46 +46 @@ 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_.