Practical guide
Aurora Serverless v2 pricing: calculate average ACU-hours
estimate Aurora Serverless v2 compute from ACU usage. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
Use time-weighted capacity, not the configured maximum
Aurora Serverless v2 compute depends on capacity over time. A maximum ACU setting is a ceiling, not proof that the database uses that capacity every hour. To estimate compute, multiply each period’s capacity by its duration and sum the ACU-hours.
The calculator focuses on Serverless v2 compute for Standard or I/O-Optimized in US East. It does not estimate the entire database bill or infer actual capacity from the minimum and maximum settings.
Worked example: daytime and overnight demand
Suppose a hypothetical database uses four ACUs for eight hours per day and one ACU for the other 16 hours. Daily compute usage is 4 × 8 + 1 × 16 = 48 ACU-hours.
Over a 30-day month, usage is 1,440 ACU-hours across 720 hours. The time-weighted average is therefore two ACUs. Entering four as the average would double this example’s compute estimate; entering one would halve it.
If a reader has its own capacity usage, include its measured ACU-hours separately. For example, another 720 ACU-hours raises the combined total to 2,160. Do not assume that adding a reader leaves compute unchanged simply because storage belongs to the same cluster.
Build a forecast from observed periods
Measure a normal business period, a quiet period, and maintenance or batch activity. A short peak can matter less than a moderately higher baseline that persists all month. Keep both capacity and duration in the worksheet so a proposed query optimization can be evaluated against the hours it actually affects.
The compute-only result excludes storage, Standard I/O requests, backup, transfer, and other components. Standard and I/O-Optimized also have different non-compute economics, so comparing only their ACU rates is not a complete purchasing decision.
For environments that may pause, verify engine and configuration support and measure the actual billable period rather than assuming all idle hours are free.
Frequently asked questions
Should I use maximum ACUs as average capacity? Only if that is genuinely the sustained usage assumption.
Does the result cover storage and I/O? No. Add those separately using the selected Aurora configuration’s billing rules.
Calculate your scenario
Use the aurora cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.