AWS Gives CloudFormation an Express Mode That Skips Stabilization Checks, Claiming Up to 4x Faster Deployments
AWS added an Express mode to CloudFormation that ends deployments once configuration is applied instead of waiting for resources to stabilize, available in all commercial Regions at no extra cost.
Overview
Amazon Web Services has added a new deployment option to CloudFormation, its infrastructure-as-code service, aimed at shortening the wait developers face when provisioning cloud resources. Announced on June 30, 2026, Express mode “accelerates deployments by completing when CloudFormation confirms resource configuration is applied, rather than waiting for extended stabilization checks,” according to the AWS News Blog. AWS says the change can reduce deployment time by up to four times for iterative development workflows and production scenarios.
What We Know
The feature changes when CloudFormation considers a deployment finished. In the default behavior, a stack operation waits for each resource to become fully usable before reporting success — a step the AWS Infrastructure-as-Code team calls stabilization. “Stabilization means that when a stack operation reports CREATE_COMPLETE, the resources can serve traffic,” the AWS DevOps Blog explains. Express mode instead completes “when resource configuration is applied, without waiting for stabilization checks,” according to the AWS News Blog, with resources continuing to become operational in the background.
AWS illustrated the difference with two examples. Creating an Amazon SQS queue with a dead letter queue takes 64 seconds in Standard mode but completes in up to 10 seconds under Express mode, and deleting an AWS Lambda function with a network interface attachment drops from 20–30 minutes to up to 10 seconds, the AWS News Blog reported. The DevOps team offered a further case: Express mode “turns a 5-10 minute CloudFront deployment into a sub-minute confirmation,” according to the AWS DevOps Blog.
The speed comes with a behavioral trade-off. “Express mode disables rollback by default for the fastest iteration experience,” the AWS News Blog noted. The DevOps team framed that as a benefit for development loops: “If a resource fails to configure, the stack stays in place and you can fix and retry immediately,” per the AWS DevOps Blog.
Developers can opt in without changing their templates. The mode is exposed through a {"mode": "EXPRESS"} deployment-config option on the CLI, and AWS’s higher-level tools carry matching flags — cdk deploy --express for the Cloud Development Kit and sam deploy --express or sam sync --express for the Serverless Application Model, according to the AWS DevOps Blog. The AWS News Blog states that Express mode is available today in all AWS commercial Regions at no additional cost.
Among the workflows AWS positions the mode for are tight-feedback-loop development and AI agent workflows, according to the AWS DevOps Blog.
Background
Express mode is the latest step in a multi-year effort to speed up CloudFormation’s provisioning. In March 2024, AWS reworked stack creation to run “up to 40% faster,” as InfoQ reported at the time. That change split resource handling “into two phases (creation and stabilization), which allows for creating other resources in the stack earlier,” per InfoQ, overlapping work that had previously run in sequence. Express mode goes further by letting a deployment report success before stabilization finishes at all.
What We Don’t Know
AWS’s headline figures are framed as ceilings — “up to” four times faster, and “up to 10 seconds” in the cited examples — so real-world gains will vary by stack composition and resource type. Because Express mode returns before resources have fully stabilized, a template that completes may still reference resources that are not yet ready to serve traffic; AWS has not published a comprehensive list of which resource types carry the largest gaps between configuration and readiness. The disabled-by-default rollback behavior also shifts more failure handling onto the operator, and AWS’s guidance on when Standard mode remains the safer choice for production traffic will shape how widely teams adopt the faster path.