Quick Answer
AWS announced on August 5, 2026 that Aurora Serverless can reach up to 12 Aurora Capacity Units within a second during scale-up and continue toward 256 ACUs, then scale down to zero after demand ends. The improvement is enabled by default for clusters on platform version 3 or 4. Existing platform-version 1 or 2 clusters must upgrade to the latest platform version 4 to receive it.
That makes Aurora Serverless a stronger candidate for bursty agent workloads, but it does not guarantee one-second application recovery, zero queueing, a specific transaction latency, or lower total cost. Validate the exact engine, Region, platform version, connection pattern, query mix, minimum and maximum ACUs, and downstream limits under a replayable burst.
What Changed—and What Did Not
| AWS announcement | Deployment boundary |
|---|---|
| Up to 12 ACUs within a second during scale-up | “Up to” is a capacity behavior, not an end-to-end request-latency guarantee |
| Continued scale up to 256 ACUs | Cluster limits, query design, connections, locks, storage, and downstream systems can still bottleneck |
| Scale down to zero | Cold or resumed behavior and the first user-visible request need testing |
| Default on platform versions 3 and 4 | Platform versions 1 and 2 require an upgrade; engine and Region support still matter |
| Pay for what you use positioning | Actual cost depends on ACU-seconds, I/O mode, storage, backups, data transfer, and related services |
Agentic Workload Readiness Test
Build a trace from the real agent path: request arrival, tool selection, database connection, queries, retries, transaction completion, model calls, and response. Replay a quiet-to-burst transition with the same concurrency and data distribution expected in production.
Measure at least:
- platform version, engine version, Region, minimum and maximum ACUs;
- time from burst arrival to capacity, connection acquisition, and successful transaction;
- p50, p95, and p99 request latency plus error, timeout, lock, and retry rates;
- active connections, pool behavior, query plans, CPU, memory, I/O, and ACU history;
- scale-down, resume, scheduled maintenance, failover, and rollback behavior;
- full cost across database, I/O, storage, backup, transfer, observability, and dependent services.
Do not change the platform version and application architecture in the same experiment if you need to attribute the outcome.
Upgrade and Rollback Gate
For a platform-version upgrade, confirm AWS’s current engine compatibility, maintenance behavior, backup or restore plan, change window, alarms, and rollback path. Run the same acceptance workload before and after the change. A console field proving version 4 is necessary evidence, but it is not proof that the application met its latency and cost objectives.
Use the Aurora Serverless agent workload readiness tool to turn the environment and workload facts into a test checklist.
Frequently Asked Questions
Does Aurora Serverless always add 12 ACUs in one second?
AWS says it can reach up to 12 ACUs within a second. Treat that as the announced capacity behavior and validate the application result under the exact cluster and workload.
Which platform versions receive faster scaling?
AWS says the enhancement is enabled by default on platform versions 3 and 4. Version 1 and 2 clusters can upgrade to the latest platform version 4.
Can Aurora Serverless scale to zero after a burst?
AWS says it automatically scales down to zero when the workload finishes. Test eligibility, timing, resume behavior, and the first request under the live configuration.
Does faster scale-up guarantee lower cost?
No. Measure the full bill and accepted workload. More responsive capacity can still change ACU duration, retries, I/O, connection behavior, and dependent-service use.
Official Sources
Source check: August 15, 2026. Recheck current engine, Region, platform-version, quota, pricing, and operational documentation before deployment.