AWS organizations documentation change
Summary
Updated 'AWS CloudFormation' to 'CloudFormation' in SCP policy example explanation
Security assessment
Branding change in service control policy example. The security implications of the policy example remain unchanged.
Diff
diff --git a/organizations/latest/userguide/orgs_manage_policies_scps_examples_tagging.md b/organizations/latest/userguide/orgs_manage_policies_scps_examples_tagging.md index eaace6a8a..36b0f836b 100644 --- a//organizations/latest/userguide/orgs_manage_policies_scps_examples_tagging.md +++ b//organizations/latest/userguide/orgs_manage_policies_scps_examples_tagging.md @@ -26 +26 @@ Remember to test Deny-based policies with the services you use in your environme -The following example policy is not compatible with AWS CloudFormation as written, because that service creates a secret and then tags it as two separate steps. This example policy effectively blocks AWS CloudFormation from creating a secret as part of a stack, because such an action would result, however briefly, in a secret that is not tagged as required. +The following example policy is not compatible with CloudFormation as written, because that service creates a secret and then tags it as two separate steps. This example policy effectively blocks CloudFormation from creating a secret as part of a stack, because such an action would result, however briefly, in a secret that is not tagged as required.