AWS launches Express mode for faster CloudFormation

AWS has launched Express mode for CloudFormation, available in all AWS commercial regions.

The option changes when a CloudFormation deployment is treated as complete. Instead of waiting for longer stabilisation checks to finish, it ends the process once resource configuration has been applied. AWS says this can cut deployment times by as much as fourfold in some development and production workflows.

CloudFormation is Amazon's infrastructure-as-code service, used by developers and operations teams to create, update, and delete cloud resources through templates. In standard mode, deployments continue running after configuration is applied while the service waits for resources to reach a fully stabilised state.

Express mode is intended for cases where teams do not need to wait for those checks before moving to the next step. Examples include iterative development, testing individual application components, and AI-assisted infrastructure work where faster feedback loops matter.

Under the new mode, resources continue becoming operational in the background after the deployment is marked complete. CloudFormation will automatically retry dependent resources that hit transient provisioning failures within the same stack.

How it differs

The new setting does not change how resources are provisioned, but it does change the point at which CloudFormation reports success. That matters for teams that want faster stack operations without rewriting existing templates.

Express mode works with all existing CloudFormation templates and supports features including change sets and nested stacks. If a parent stack uses Express mode, nested stacks will use it as well.

The service can be enabled through the AWS Management Console, the AWS Command Line Interface, software development kits, and infrastructure tools including AWS Cloud Development Kit. In CDK, users can deploy with an express flag that routes the generated CloudFormation template through the new mode.

No template changes are required. Rollback is disabled by default in Express mode to support faster iteration, although users can turn it back on for production environments by changing the deployment configuration.

Speed claims

AWS illustrated the timing difference with several examples from internal benchmarking. Creating an Amazon SQS queue with a dead-letter queue took 64 seconds in standard mode but as little as 10 seconds in Express mode, according to the company.

In another example, deleting an AWS Lambda function with a network interface attachment took 20 to 30 minutes in standard mode, compared with as little as 10 seconds in Express mode. The largest gains appear to come from operations where stabilisation checks or clean-up tasks extend completion times well beyond the point of initial configuration.

The launch also reflects the growing influence of AI-assisted software development on cloud tooling. AWS explicitly positioned Express mode for developers and AI tools that repeatedly modify infrastructure and need rapid confirmation that a change has been accepted.

That suggests AWS is trying to make infrastructure-as-code workflows behave more like application development cycles, where quick iteration is central. For engineers testing a role, function, queue, or event source mapping one step at a time, waiting for every resource to fully stabilise can slow each pass through the loop.

Operational trade-off

The trade-off is that a deployment can show as complete before resources are ready to serve traffic or before every background stabilisation step has finished. Teams that need resources to be fully operational before testing or directing live traffic should continue using the default deployment behaviour, AWS says.

That means Express mode is likely to appeal most to developers working in lower-risk environments, platform teams making incremental changes, and organisations with monitoring and clean-up processes that can handle failed deployments after early completion. It may be less suitable for workloads where downstream systems depend on immediate operational readiness.

By supporting existing templates and stack features, AWS appears to be lowering the barrier for current CloudFormation users to try the new mode. The absence of extra charges may also help adoption among teams already standardised on the service.

Express mode is offered at no additional cost.