Five times the execution count, ten times the start rate
AWS has increased the default quotas for Lambda durable functions. The normal allowance for running durable executions rises from one million to five million per account and Region. The rate for starting them increases from 300 to 3,000 requests per second.
These are durable-workflow limits. They should not be read as a promise that five million ordinary Lambda function invocations can consume compute simultaneously. Durable workflows can also wait for external work.
Three Regions have higher defaults
AWS lists double these limits in US East, Northern Virginia; US West, Oregon; and Europe, Ireland. The current documentation shows 10 million running durable executions and 6,000 start requests per second there.
Other API limits also increase. Checkpoint and state-read calls normally allow 10,000 requests per second; execution-history and execution-list calls allow 150. The same three Regions receive double those figures.
What application operators can check
The changes apply wherever Lambda durable functions is available. Operators can compare their workload’s Region and quota settings with the linked table before changing traffic or monitoring rates.
The execution-count limit is adjustable. Separate restrictions remain, including a maximum of 30,000 durable operations per execution and a 1 MB payload per operation. The announcement changes capacity limits; it does not announce a price cut.
