Deploy Infrastructure Faster with AWS CloudFormation Express Mode

Introduction

If you’ve spent time working with AWS CloudFormation, you’ve probably hit that frustrating moment where you’re sitting around watching a deployment tick along, waiting for resources to stabilize — even though all you really changed was a parameter value or a tag. That wait adds up fast, especially when you’re in the middle of active development or iterating on infrastructure alongside an AI-assisted workflow.

CloudFormation Express mode is AWS’s answer to that problem. It’s a deployment option that marks a stack operation as complete once the resource configuration is successfully applied, without delaying the process until the resource fully stabilises. The result? Deployments that can finish up to four times faster than standard mode, sometimes in under a minute.

Resources don’t just get abandoned, though. They continue to stabilise in the background, and CloudFormation still handles transient failures and automatically retries dependent resources. The key difference is that you don’t have to wait for all of that to finish before you can move on.

How AWS CloudFormation Express Mode Works?

Standard CloudFormation follows a clear sequence: apply the resource configuration, then wait for resources to reach a stable, operational state. Only then does it consider the deployment done. That stabilisation step exists for good reason — it’s what makes CloudFormation dependable for production workloads.

Express mode skips the waiting part. Once CloudFormation has confirmed the configuration was applied successfully, it marks the deployment complete. Resources keep progressing toward their operational state, but this happens asynchronously and is outside your critical path.

Where this matters most:

– Infrastructure development: You want to test and tweak configurations quickly without long wait times between iterations.

– Component testing: You’re deploying individual pieces of infrastructure and don’t need the full stack operational before checking your work.

– AI-assisted development: AI tools that make infrastructure changes benefit enormously from sub-minute feedback cycles. Express mode makes that possible.

– Production use cases (selective): If your application can handle resources becoming fully available asynchronously, Express mode can work here too.

One thing worth being clear on: Express mode doesn’t change how resources are provisioned. AWS still provisions them the same way. The only thing that changes is when CloudFormation calls the deployment “done.”

To put some real numbers on it, from my own benchmarking:

– Removing a Lambda function with an attached network interface: ~20–30 minutes in Standard mode vs. about 10 seconds in Express mode.

– Updating an API Gateway configuration: ~60–90 seconds in Standard mode vs. roughly 10 seconds in Express mode.

Those aren’t minor differences. In a development context, that’s the difference between a frustrating workflow and a smooth one.

Enabling CloudFormation Express Mode

1. Via the AWS Console

When creating a new CloudFormation stack through the AWS Management Console, you’ll find the Express mode option under Stack deployment options. Enable it before submitting the stack creation.

2. Via AWS CLI

Pass EXPRESS as the value for the –deployment-config parameter when running stack create, update, or delete commands. No changes to your existing CloudFormation template are required — it works with whatever you already have.

A couple of things to note here: Express mode turns off rollback by default, which keeps things moving quickly. If you’re using it in a production context and still want rollback behaviour, you can enable it by setting disableRollback to false in the deployment config. It’s also worth setting up some monitoring or a cleanup process for deployments that don’t complete successfully.

3.Via AWS CDK

If you’re working with CDK, the command is straightforward:

cdk deploy –express

CDK generates the CloudFormation template as usual and submits it through Express mode. Nothing else changes about how your CDK code works.

A few other things worth knowing:

– Express mode works with existing templates — no modifications needed.

– Change sets and nested stacks are supported. When you enable Express mode on a parent stack, nested stacks automatically follow suit.

– If your workflow requires resources to be fully operational before traffic is shifted or tests are run, stick with standard mode. Express mode is not the right tool for every situation.

Conclusion

AWS CloudFormation Express mode solves a real pain point for anyone who spends meaningful time iterating on infrastructure. By decoupling deployment completion from resource stabilisation, this approach turns multi-minute wait times into sub-minute feedback loops — without requiring any changes to your existing templates or CDK code.

It’s not a replacement for standard mode. In production environments where you need resources to be fully operational before anything else happens, the stabilisation checks in standard mode are doing important work. But for development, component testing, and AI-assisted infrastructure workflows, Express mode is genuinely useful and worth adopting.