AWS controltower documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' in two locations for consistency
Security assessment
Changes are purely terminological (branding update) without altering security context. No vulnerability or security feature is mentioned.
Diff
diff --git a/controltower/latest/controlreference/compliance.md b/controltower/latest/controlreference/compliance.md index 809735d4d..d52325cab 100644 --- a//controltower/latest/controlreference/compliance.md +++ b//controltower/latest/controlreference/compliance.md @@ -17 +17 @@ When we talk about compliance in AWS Control Tower, we do not intend the same me - * For more information about how you can verify AWS Control Tower resource compliance during AWS CloudFormation stack creation, see this blog post, [How AWS Control Tower users can proactively verify compliance in AWS CloudFormationstacks](https://aws.amazon.com/blogs/mt/how-aws-control-tower-users-can-proactively-verify-compliance-in-aws-cloudformation-stacks/). + * For more information about how you can verify AWS Control Tower resource compliance during CloudFormation stack creation, see this blog post, [How AWS Control Tower users can proactively verify compliance in AWS CloudFormationstacks](https://aws.amazon.com/blogs/mt/how-aws-control-tower-users-can-proactively-verify-compliance-in-aws-cloudformation-stacks/). @@ -24 +24 @@ For ongoing governance, administrators can enable pre-configured controls—clea - * Prevent deployment of resources that don’t conform to policies (by means of preventive controls, implemented with SCPs, or by means of proactive controls, implemented with AWS CloudFormation hooks). + * Prevent deployment of resources that don’t conform to policies (by means of preventive controls, implemented with SCPs, or by means of proactive controls, implemented with CloudFormation hooks).