AWS pinpoint documentation change
Summary
Updated reference from 'AWS CloudFormation' to 'CloudFormation' in IAM policy condition example
Security assessment
The change is a minor terminology adjustment (removing redundant 'AWS' prefix from CloudFormation service name) without altering security guidance. No evidence of addressing vulnerabilities or modifying security controls.
Diff
diff --git a/pinpoint/latest/developerguide/security_iam_id-based-policy-examples.md b/pinpoint/latest/developerguide/security_iam_id-based-policy-examples.md index 3e8489b0e..b92c807fc 100644 --- a//pinpoint/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//pinpoint/latest/developerguide/security_iam_id-based-policy-examples.md @@ -48 +48 @@ 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_.