AWS AWSCloudFormation documentation change
Summary
Added notes about automatic pre-deployment validation and clarified that change sets provide additional benefits over direct updates
Security assessment
The changes emphasize validation best practices and change set advantages. No security vulnerabilities or security-specific features are referenced, only general error prevention.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/best-practices.md b/AWSCloudFormation/latest/UserGuide/best-practices.md index 24c3f6b6a..30d87202c 100644 --- a//AWSCloudFormation/latest/UserGuide/best-practices.md +++ b//AWSCloudFormation/latest/UserGuide/best-practices.md @@ -120,0 +121,2 @@ For a step-by-step, hands-on walkthrough on how to use both tools to shorten the +CloudFormation pre-deployment validation automatically catches common errors before any resources are provisioned. These errors include invalid property syntax and resource name conflicts. Pre-deployment validation runs by default on all Create Stack, Update Stack, and Create Change Set operations. No configuration is required. For CDK projects, `cdk validate` runs CloudFormation pre-deployment validation against your synthesized templates. + @@ -296,0 +299,4 @@ Use change sets to check how your changes might impact your running resources, e +###### Note + +If you use direct stack updates instead of change sets, pre-deployment validation still validates your templates automatically. However, change sets provide additional benefits. Use change sets to preview which resources will be added, modified, or replaced before you execute the update. +