If you've ever deployed a CloudFront distribution through CDK and watched it sit at CREATE_IN_PROGRESS for 15 minutes while it propagates to edge locations, you know the pain. You also know you're not getting those 15 minutes back.
CloudFormation Express mode changes that. It completes when resource configuration is applied, rather than waiting for full stabilization. Up to 4x faster for iterative workflows.
What Stabilization Actually Costs You
Every CloudFormation deployment has two phases: applying configuration and then running stabilization checks. The stabilization phase confirms things like traffic readiness, region propagation, and resource cleanup. For production traffic cutover, that matters. For the 47th iteration of your CDK stack during development, it doesn't.
Some numbers from the AWS announcement:
- SQS queue with a DLQ: Standard mode takes ~64 seconds. Express mode: ~10 seconds.
- Deleting a Lambda with a network interface: Standard mode takes 20–30 minutes. Express mode: ~10 seconds.
- CloudFront distribution changes: Minutes of propagation checks that don't affect whether your config is correct.
That last one is what drove me to pay attention to this. CloudFront deployments in my CDK stacks are the single biggest time sink. Not because the config is wrong, but because CloudFormation waits for global propagation before marking the resource complete. During development, I do not care if all 400+ edge locations have the new config yet. I care that the configuration was accepted.
How Express Mode Works
Express mode doesn't change how resources are provisioned. It changes when the deployment is marked complete.
Standard mode:
Create resource → Apply config → Wait for stabilization → Mark complete
Express mode:
Create resource → Apply config → Mark complete (stabilization continues in background)
Resources continue becoming operational after the deployment finishes. CloudFormation automatically retries dependent resources that hit transient failures during provisioning. If resource B depends on resource A and A hasn't fully stabilized yet, CloudFormation handles the retry internally without you needing to do anything.
It's worth being clear about: Express mode is not skipping provisioning steps. It's skipping the verification that those steps finished. The resources still get created the same way. You just don't sit there watching them.
Using It
CLI
Add --deployment-config to any create, update, or delete operation:
aws cloudformation create-stack \
--stack-name my-app \
--template-body file://template.yaml \
--deployment-config '{"mode": "EXPRESS", "disableRollback": true}'
Express mode disables rollback by default to keep iteration fast. For production, set disableRollback to false explicitly.
CDK
For CDK users, it's even simpler:
cdk deploy --express
No template changes, no construct modifications. It works with all existing templates, change sets, and nested stacks. Enable it on a parent stack and nested stacks inherit it automatically.
When to Use It and When Not To
Express mode is for any deployment where your next step is "check that the config looks right and iterate again." Development, testing, AI-assisted infrastructure work where you want sub-minute feedback loops.
Standard mode is for when your next step is "send production traffic." Blue/green cutover, canary deployments, anything where "resource is configured" and "resource is ready to serve" need to be the same moment.
Make It Your Default for Development
If you're iterating on infrastructure with CDK, cdk deploy --express should be your default. Save Standard mode for when you actually need stabilization guarantees. For everything else, there's no reason to wait.
