CloudFormation and CDK catch deploy errors in seconds, before provisioning!

Hey there, it's me, Shii-chan! Today I found an update that CloudFormation users are going to be happy about, so let me tell you about it.

AWS What's New aws.amazon.com

What was announced?

Over on AWS's What's New, AWS CloudFormation and CDK announced that their pre-deployment validation now runs on all Create Stack and Update Stack operations, checking for errors before your operation kicks off. Instead of the old "create -> fail -> roll back" cycle, it can tell you "hey, this part is broken" in just seconds.

The story so far

Pre-deployment validation already existed, but only when you created a change set. It caught things like property syntax errors, resource name conflicts, and whether an S3 bucket was empty. So if you just called Create Stack or Update Stack directly, provisioning would start and you'd only notice the failure after it happened.

What changes

Now the same validation runs automatically on Create Stack and Update Stack too. It's on by default with no configuration needed. Whether you're iterating by hand, running a CI/CD pipeline, or letting an AI agent build infrastructure, you find out "this is the problem" before anything fails, complete with the logical resource ID and property path, so you can fix it and then deploy. That's a nice boost to your development tempo.

Dive Deep

Three new checks were added as warnings during change set creation:

• Service quota limits: warns when creating resources would exceed your account's service quotas
• AWS Config Recorder conflict detection: warns when you add Config rules to an account without Config recording enabled, or define a Config Recorder where one is already active
• ECR repository delete readiness: warns when an ECR repository targeted for deletion still contains images

You can view errors through the DescribeEvents API, or in the console by following the operation ID from your stack's Events tab to the "Deployment validations" tab. In CDK, both cdk deploy and cdk validate return results with construct-level tracing, so AI agents and automation tools can parse the structured response and self-correct right away.

If you want to skip validation, use the new DisableValidation parameter on CreateStack / UpdateStack / CreateChangeSet, or the --disable-validation flag in the CLI.

It's available in all Regions where CloudFormation is supported, excluding China.

Wrap-up

• CloudFormation's pre-deployment validation now covers all Create Stack / Update Stack operations
• Three new change-set warnings added: quotas, Config Recorder, and ECR delete readiness
• On by default, with DisableValidation to skip when needed
• CDK returns results via cdk deploy / cdk validate, handy for AI agent self-correction
• Available in all CloudFormation Regions except China

This one's for IaC fans who want to fix things fast without waiting for failures, and anyone auto-deploying with CI/CD or AI agents!