AWS CloudFormation and CDK express mode speeds up infrastructure deployments by up to 4x
Skip the wait: CloudFormation Express Mode cuts deployment times up to 4x by completing once config is applied, not after full stabilization.
View original announcement →Visual Summary
graph TD
A{{CloudFormation Express Mode}}:::announced
B((Developer)):::external
C((AI Agent)):::external
D(AWS CDK):::compute
E(AWS CLI / SDK):::compute
F([4x Faster Deployment]):::feature
G([No Rollback Default]):::feature
H([Background Propagation]):::feature
I(CloudFormation Stacks):::compute
J(AWS Resources):::storage
B ==>|"cdk deploy --express"| D
C ==>|"--mode EXPRESS"| E
D -->|"synthesizes"| A
E -->|"activates"| A
A -->|"deploys"| I
I -->|"provisions"| J
A -->|"enables"| F
A -.->|"disables rollback"| G
J -.->|"async stabilization"| H
classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold
classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0
classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32
classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100
classDef external fill:#f5f5f5,stroke:#616161,color:#616161
What's New
AWS has introduced Express Mode for CloudFormation and CDK, a new deployment configuration that reduces infrastructure deployment times by up to 4x compared to the default mode. Instead of waiting for full resource stabilization (e.g., traffic readiness, region propagation, and resource cleanup), Express Mode marks a stack operation complete as soon as the resource configuration API call succeeds. This feature targets developers and AI agents engaged in iterative infrastructure development, enabling dramatically faster feedback loops without requiring any template changes.
How It Works
- Completion trigger: Express Mode considers a resource operation complete as soon as the underlying API call to create, update, or delete the resource succeeds, rather than waiting for the resource to reach a fully stabilized operational state.
- Background propagation: Post-configuration tasks such as CloudFront edge propagation, traffic readiness checks, and resource cleanup continue asynchronously in the background after the deployment is marked complete.
- Dependency ordering preserved: CloudFormation still processes resources in their declared dependency order and handles failures of dependent resources within the same stack, maintaining correctness guarantees.
- Rollback disabled by default: Express Mode disables automatic rollback, allowing developers to immediately fix errors and retry without waiting for rollback operations to complete.
- CLI activation: Enable via
--deployment-config '{"mode": "EXPRESS"}'oncreate-stack,update-stack,delete-stack, andcreate-change-setcommands in the AWS CLI or SDKs. - CDK activation: CDK users simply run
cdk deploy --express— no changes to CDK app code or CloudFormation templates are required. - Nested stack support: Express Mode works with nested stacks and all existing CloudFormation templates without modification.
Why It's Important
- Dramatically faster iteration cycles: Deployments that previously took 5–10 minutes (e.g., creating a CloudFront distribution waiting for global edge propagation) can now complete in seconds, fundamentally changing the inner-loop development experience.
- AI agent enablement: As AI coding agents increasingly provision and iterate on infrastructure autonomously, faster deployment confirmation allows agents to proceed through multi-step workflows without long blocking waits, improving overall agent efficiency.
- No template changes required: Adoption has zero migration cost — existing templates, stacks, and CDK apps work immediately with Express Mode via a single flag.
- Immediate fix-and-retry: Disabling rollback by default means failed deployments don't incur additional wait time for rollback operations, letting developers correct and redeploy faster.
- Decouples configuration from stabilization: Developers who only need an output value (e.g., a CloudFront domain name) to continue their work are no longer blocked by stabilization checks irrelevant to their immediate need.
How It's Different
- vs. Default CloudFormation mode: Default mode waits for full resource stabilization (running state, traffic readiness, propagation) before marking a deployment complete; Express Mode completes as soon as the configuration API call succeeds.
- vs. CDK Hotswap deployments: CDK hotswap bypasses CloudFormation entirely for specific resource types (e.g., Lambda function code) to achieve speed; Express Mode works through the standard CloudFormation engine and applies to all resource types universally.
- Rollback behavior: Default mode automatically rolls back on failure; Express Mode disables rollback by default, prioritizing speed and immediate retry over automatic state recovery.
- Scope of applicability: Express Mode works with all existing CloudFormation templates and nested stacks with no modifications, whereas hotswap is limited to a specific set of supported resource types.
- Stabilization guarantees: Default mode guarantees resources are fully operational before reporting success; Express Mode explicitly trades that guarantee for speed, making it unsuitable for production deployments where operational readiness must be confirmed.
When to Prefer It
- Iterative development workflows: When rapidly prototyping or iterating on infrastructure templates and you need quick confirmation that resource configurations are syntactically and semantically valid.
- CI/CD dev/test pipelines: When running automated pipelines in non-production environments where deployment speed matters more than waiting for full resource stabilization.
- AI agent-driven infrastructure: When an AI agent is building or modifying infrastructure incrementally and needs fast feedback to proceed to the next step in a multi-action workflow.
- Output-dependent workflows: When you only need a resource output value (e.g., an ARN, endpoint URL, or domain name) to continue development and do not need the resource to be fully operational.
- High-frequency iteration loops: When making many small, incremental template changes and the cumulative wait time of default stabilization checks significantly slows down development velocity.
- Avoid for production deployments: Do not use Express Mode when deploying to production environments where you must verify that all resources are fully stabilized, operational, and ready to serve traffic before considering the deployment successful.
Availability
- GA status: Generally Available as of June 30, 2026 — no preview or beta restrictions noted.
- Regional availability: Available in all AWS Regions where AWS CloudFormation is supported, covering all standard commercial, GovCloud, and other partitions where CloudFormation is offered.
- Pricing: No additional charge for Express Mode; standard CloudFormation pricing applies (CloudFormation itself has no charge for stack operations on most resource types, with costs driven by the underlying resources provisioned).
- Unsupported features/limitations: Automatic rollback is disabled by default in Express Mode; resources may not be fully operational or ready to serve traffic when the deployment reports completion; not recommended for production use cases requiring full stabilization guarantees.
- Interface support: Available via AWS CLI, AWS SDKs, AWS Management Console (CloudFormation console), and AWS CDK (
cdk deploy --express). - Template compatibility: Works with all existing CloudFormation templates and nested stacks — no template modifications required.
Related Resources
- https://docs.aws.amazon.com/cloudformation/
- https://docs.aws.amazon.com/cdk/v2/guide/home.html
- https://docs.aws.amazon.com/cli/latest/reference/cloudformation/
- https://console.aws.amazon.com/cloudformation
- https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-express-mode.html
- https://docs.aws.amazon.com/general/latest/gr/cfn.html#cfn_region
