AWS Security ChangesHomeSearch

AWS whitepapers documentation change

Service: whitepapers · 2025-10-01 · Documentation low

File: whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.md

Summary

Fixed typo in 'launches' and added JSON section markers

Security assessment

Minor grammatical correction and document structure changes. No security content additions or vulnerability fixes.

Diff

diff --git a/whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.md b/whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.md
index 06deb1090..cc03517db 100644
--- a//whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.md
+++ b//whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.md
@@ -32 +32 @@ You can easily define a resource group based on the AWS CloudFormation stack. Th
-[AWS CloudFormation Hooks](https://aws.amazon.com/blogs/mt/proactively-keep-resources-secure-and-compliant-with-aws-cloudformation-hooks/) provide developers with a means of keeping key aspects of their application consistent with their organization’s standards. Hooks can be configured to provide a _warning_ or _prevent deployment_. This feature is best suited to checking key configuration elements in your templates, such as whether an Auto Scaling group is configured to apply customer defined tags to all the Amazon EC2 instances it will launches, or to ensure that all Amazon S3 buckets are created with the required encryption settings. In both cases, evaluation of this compliance is being pushed to the earlier in the deployment process with AWS CloudFormation hooks before deployment. 
+[AWS CloudFormation Hooks](https://aws.amazon.com/blogs/mt/proactively-keep-resources-secure-and-compliant-with-aws-cloudformation-hooks/) provide developers with a means of keeping key aspects of their application consistent with their organization’s standards. Hooks can be configured to provide a _warning_ or _prevent deployment_. This feature is best suited to checking key configuration elements in your templates, such as whether an Auto Scaling group is configured to apply customer defined tags to all the Amazon EC2 instances it launches, or to ensure that all Amazon S3 buckets are created with the required encryption settings. In both cases, evaluation of this compliance is being pushed to the earlier in the deployment process with AWS CloudFormation hooks before deployment. 
@@ -182,0 +183,6 @@ The following is a deny SCP:
+JSON
+    
+
+****
+    
+