.png)
Key takeaways
1
Treat 69% as a ceiling, not a default: compare current offers for your exact engine, class, Region, deployment, and term.
2
Size flexibility changes the matching rules.
3
Extended Support can erase the gain.
4
Database Savings Plans trade depth for flexibility.
RDS Reserved Instances are billing commitments that reduce eligible Amazon RDS instance charges in exchange for a one-year or three-year term. Nothing changes about the database itself.
AWS applies the billing benefit automatically to eligible usage, and AWS states that Reserved Instances can save up to 69% versus On-Demand pricing for steady-state workloads (AWS RDS pricing). The actual discount depends on the engine, instance class, Region, term, payment option, and current offering.
Stable production databases are natural candidates for commitment discounts, but only after you confirm the workload is correctly sized, on a supported engine version, and likely to remain at a predictable baseline.
For current discount ranges by engine, use the RDS Reserved Instance pricing guide.
At purchase, you select the database product, instance class, Region, term, payment option, and deployment option offered in the console. The commitment continues for the term even if you stop or delete the database.
AWS applies the billing benefit automatically to eligible usage, and AWS states that Reserved Instances can save up to 69% versus On-Demand pricing for steady-state workloads (AWS RDS pricing). The actual discount depends on the engine, instance class, Region, term, payment option, and current offering.
Stable production databases are natural candidates for commitment discounts, but only after you confirm the workload is correctly sized, on a supported engine version, and likely to remain at a predictable baseline.
For current discount ranges by engine, use the RDS Reserved Instance pricing guide.
What RDS Reserved Instances actually do
An RDS Reserved Instance is a billing benefit, not a separate database. You keep running the same DB instance while AWS applies a discounted reservation rate to eligible usage.At purchase, you select the database product, instance class, Region, term, payment option, and deployment option offered in the console. The commitment continues for the term even if you stop or delete the database.
| Payment Option | Term Availability | Payment Structure |
|---|---|---|
| No Upfront | One year; subject to AWS approval | Discounted hourly charges |
| Partial Upfront | One or three years where offered | Part upfront, part hourly |
| All Upfront | One or three years where offered | Full reservation cost upfront |
Available Reserved Instance offerings can vary by configuration, so confirm current availability and pricing in the console or with the RDS CLI before purchasing.
Exact rates vary by Region, engine, class, deployment, and purchase date. Compare the effective reservation cost against the On-Demand cost for the same eligible usage.
Calculation block: annual eligible DB instance-charge savings
How much can RDS RIs save?
AWS advertises savings of up to 69% over On-Demand rates for steady-state RDS workloads (AWS RDS pricing). That is a maximum, not a standard discount for every configuration.Exact rates vary by Region, engine, class, deployment, and purchase date. Compare the effective reservation cost against the On-Demand cost for the same eligible usage.
Calculation block: annual eligible DB instance-charge savings
Annual eligible DB
instance-charge savings
instance-charge savings
=
(On-Demand hourly cost − effective reserved hourly cost)
× 8,760 × matching capacity
This figure covers only eligible DB instance charges. It excludes storage, backup, I/O, data transfer, and Extended Support charges, which AWS bills separately at On-Demand rates and which Reserved Instance discounts do not reduce (AWS RDS pricing).
Apply this only after right-sizing. Reserving an oversized database discounts waste rather than removing it.
For term selection, see the one-year versus three-year RDS RI guide.
AWS documents size-flexible Reserved DB Instances for Db2, MariaDB, MySQL, Oracle BYOL, and PostgreSQL. SQL Server and Oracle License Included do not receive RDS size flexibility. Aurora has separate reserved-instance rules (AWS: RDS Reserved Instances size flexibility).
For eligible engines, reservation benefits can apply across sizes within the same instance class type using normalized units. AWS also states that size-flexible benefits can move between Single-AZ and Multi-AZ configurations within that class type.
Single-AZ normalized units include micro = 0.5 units, small = 1, medium = 2, large = 4, xlarge = 8, and 2xlarge = 16. These are the Single-AZ values. A Multi-AZ DB instance consumes twice the corresponding Single-AZ units, and a Multi-AZ DB cluster consumes three times the Single-AZ units, so a highly available deployment needs a larger reservation than the raw list suggests (AWS: RDS Reserved Instances).
For example, one large reservation with 4 units can cover two medium instances with 2 units each in the same family and Region. The same 4 units cover only half of one large Multi-AZ DB instance, which consumes 8 units.
For the architecture decision, read the RDS MySQL Multi-AZ cost guide.
Apply this only after right-sizing. Reserving an oversized database discounts waste rather than removing it.
What RDS RIs don’t discount
Reserved Instance pricing covers eligible DB instance charges only, not storage, backup, I/O, data transfer, or Extended Support, which AWS bills separately at On-Demand rates (AWS RDS pricing). Evaluate those costs separately.For term selection, see the one-year versus three-year RDS RI guide.
Size flexibility changes the matching rules
For eligible engines, size-flexible RIs can apply across Single-AZ and Multi-AZ configurations within the same instance class type.AWS documents size-flexible Reserved DB Instances for Db2, MariaDB, MySQL, Oracle BYOL, and PostgreSQL. SQL Server and Oracle License Included do not receive RDS size flexibility. Aurora has separate reserved-instance rules (AWS: RDS Reserved Instances size flexibility).
For eligible engines, reservation benefits can apply across sizes within the same instance class type using normalized units. AWS also states that size-flexible benefits can move between Single-AZ and Multi-AZ configurations within that class type.
Single-AZ normalized units include micro = 0.5 units, small = 1, medium = 2, large = 4, xlarge = 8, and 2xlarge = 16. These are the Single-AZ values. A Multi-AZ DB instance consumes twice the corresponding Single-AZ units, and a Multi-AZ DB cluster consumes three times the Single-AZ units, so a highly available deployment needs a larger reservation than the raw list suggests (AWS: RDS Reserved Instances).
For example, one large reservation with 4 units can cover two medium instances with 2 units each in the same family and Region. The same 4 units cover only half of one large Multi-AZ DB instance, which consumes 8 units.
For the architecture decision, read the RDS MySQL Multi-AZ cost guide.
RDS RIs versus Database Savings Plans
Database Savings Plans materially changed this choice after launching in December 2025 (AWS: Introducing Database Savings Plans).| Dimension | RDS Reserved Instances | Database Savings Plans |
|---|---|---|
| Maximum advertised savings | Up to 69% | Up to 35% for eligible serverless usage; up to 20% for eligible provisioned database instances, including typical provisioned RDS usage |
| Term | One or three years | One year |
| Flexibility | More configuration-specific | Eligible usage can span engines, families, sizes, deployment options, and Regions |
| Provisioned discount | Can be deeper | Up to 20% across supported provisioned database services |
| Best fit | Stable baseline | Workloads expected to change |
The provisioned-instance ceiling matters for an RDS reader: AWS advertises the headline “up to 35%” for eligible serverless deployments, while provisioned instances across supported database services, including typical provisioned RDS usage, receive up to 20% (AWS: Database Savings Plans pricing).
AWS describes eligible RDS usage regardless of engine and gives a move from RDS for Oracle to Aurora PostgreSQL as an example of the plan’s portability. For RDS for SQL Server, Database Savings Plans discount the instance price, while Windows Server and SQL Server licensing charges remain outside the discount.
The same workload cannot receive both an RDS RI discount and a Database Savings Plan discount simultaneously.
Over 8,760 hours:
AWS describes eligible RDS usage regardless of engine and gives a move from RDS for Oracle to Aurora PostgreSQL as an example of the plan’s portability. For RDS for SQL Server, Database Savings Plans discount the instance price, while Windows Server and SQL Server licensing charges remain outside the discount.
The same workload cannot receive both an RDS RI discount and a Database Savings Plan discount simultaneously.
Worked example for a stable provisioned RDS baseline
Assume one continuously running eligible DB instance costs $1.00 per hour On-Demand, a matching RDS Reserved Instance has an effective hourly cost of $0.70, and a Database Savings Plan has an effective hourly cost of $0.85.Over 8,760 hours:
| Option | Illustrative Hourly Cost | Annual Cost |
|---|---|---|
| On-Demand | $1.00 | $8,760 |
| RDS Reserved Instance | $0.70 | $6,132 |
| Database Savings Plan | $0.85 | $7,446 |
In this hypothetical, the configuration-specific RI saves $1,314 more per year than the more flexible one-year plan.
Replace these illustrative rates with current AWS offers for your exact engine, class, Region, deployment, and payment option before purchasing.
AWS prices Extended Support by engine version, Region, calendar year, and vCPU count. For RDS for MySQL 5.7 in US East (Ohio), AWS states that the rate became $0.200 per vCPU-hour on March 1, 2026 (AWS RDS pricing).
Replace these illustrative rates with current AWS offers for your exact engine, class, Region, deployment, and payment option before purchasing.
Avoid the Extended Support trap
RDS Extended Support charges are separate from instance charges, so Reserved Instance discounts do not reduce them.AWS prices Extended Support by engine version, Region, calendar year, and vCPU count. For RDS for MySQL 5.7 in US East (Ohio), AWS states that the rate became $0.200 per vCPU-hour on March 1, 2026 (AWS RDS pricing).
Calculation example:
A Single-AZ four-vCPU MySQL 5.7 instance in that Region adds $0.80 per hour in Extended Support charges. Multi-AZ deployments incur Extended Support charges for the primary and standby instances.
A Single-AZ four-vCPU MySQL 5.7 instance in that Region adds $0.80 per hour in Extended Support charges. Multi-AZ deployments incur Extended Support charges for the primary and standby instances.
For the Single-AZ example, that surcharge alone equals $7,008 over 8,760 hours of continuous usage, before instance, storage, backup, or data-transfer charges.
Warning:
Extended Support charges sit outside RI discounts. Always check engine support status before buying a multi-year reservation.
Check engine support status before committing. A deep RI discount does not make an avoidable Extended Support surcharge economical.
Use the right optimization sequence
Check engine support status. Upgrade versions already in Extended Support when practical.
Right-size before reserving. Review sustained CPU, memory, connections, and workload behavior.
Confirm the deployment model. Decide whether the workload needs Multi-AZ or a Multi-AZ DB cluster.
Review the instance family. Consider newer families only after compatibility and performance testing.
Compare RI and Database Savings Plan economics using current AWS offers.
Confirm the commitment fits the stable floor. Before buying, confirm that the Region, engine, instance class, deployment type, and term match the stable floor of usage you expect to retain. AWS does not allow RDS Reserved Instances to be transferred, sold, or cancelled, and one-time fees are nonrefundable.
Review commitments after purchase. Review RI coverage and utilization monthly, and reassess commitments after changes to engine version, instance class, Region, deployment type, migration plans, or decommissioning plans.
For the procedural version, use the step-by-step RDS RI purchase walkthrough.
For size-flexible engines, normalized units can span eligible Single-AZ and Multi-AZ usage. For a Multi-AZ DB cluster, AWS documents two equivalent reservation approaches: three Single-AZ Reserved DB Instances of the same size, or one Multi-AZ Reserved DB Instance plus one Single-AZ Reserved DB Instance of the same size (AWS RDS pricing).
Aurora is different. Reserved Aurora instances use the Single-AZ reservation option, and reservation capacity is needed for each provisioned DB instance you want covered, including replicas.
See the RDS Multi-AZ DB cluster cost guide.
Multi-AZ and cluster reservations
Traditional Multi-AZ DB instances and Multi-AZ DB clusters have different reservation shapes.For size-flexible engines, normalized units can span eligible Single-AZ and Multi-AZ usage. For a Multi-AZ DB cluster, AWS documents two equivalent reservation approaches: three Single-AZ Reserved DB Instances of the same size, or one Multi-AZ Reserved DB Instance plus one Single-AZ Reserved DB Instance of the same size (AWS RDS pricing).
Aurora is different. Reserved Aurora instances use the Single-AZ reservation option, and reservation capacity is needed for each provisioned DB instance you want covered, including replicas.
See the RDS Multi-AZ DB cluster cost guide.
Engine-specific points to remember
| Engine | RI Size Flexibility | Key Constraint | Pre-Purchase Check |
|---|---|---|---|
| MySQL | Yes | Same engine, family, and Region | Confirm the version is not in Extended Support |
| MariaDB | Yes | Same engine, family, and Region | Confirm version support status |
| PostgreSQL | Yes | Same engine, family, and Region | Confirm version support status |
| Db2 | Yes | Same engine, family, and Region; licensing terms apply | Confirm license model |
| Oracle BYOL | Yes | BYOL only; License Included is excluded | Confirm BYOL vs License Included |
| Oracle License Included | No | Locked to the purchased size | Verify the exact class before buying |
| SQL Server | No | Locked to the purchased size; confirm the applicable pricing model | Verify the exact class and license impact |
| Aurora | Separate rules | Reserve each provisioned instance, including replicas | Count all instances and replicas to cover |
For a deeper example, see the RDS MySQL Reserved Instances guide.
We help teams evaluate eligible RDS commitments against actual usage patterns and manage commitment coverage as workloads evolve. The goal is to capture commitment-based savings without treating AWS’s maximum advertised discount as the expected outcome for every workload.
With our Flex Insured Commitments program, teams can capture up to 69% savings available through Amazon RDS Reserved Instances without taking on the long-term commitment risk. If a commitment no longer delivers savings compared with equivalent On-Demand usage, Usage.ai provides cashback protection to help cover the difference.
Our pricing is based on a percentage of the savings we actually deliver, so commitment decisions can remain tied to measurable savings rather than simply maximizing reservation coverage.
How we help optimize RDS commitments
Manual RDS commitment management requires repeated checks of utilization, engine lifecycle, sizing, purchase options, and workload changes.We help teams evaluate eligible RDS commitments against actual usage patterns and manage commitment coverage as workloads evolve. The goal is to capture commitment-based savings without treating AWS’s maximum advertised discount as the expected outcome for every workload.
With our Flex Insured Commitments program, teams can capture up to 69% savings available through Amazon RDS Reserved Instances without taking on the long-term commitment risk. If a commitment no longer delivers savings compared with equivalent On-Demand usage, Usage.ai provides cashback protection to help cover the difference.
Our pricing is based on a percentage of the savings we actually deliver, so commitment decisions can remain tied to measurable savings rather than simply maximizing reservation coverage.
Frequently asked questions
What is an RDS Reserved Instance?
It is a billing commitment that discounts eligible RDS instance usage for a one-year or three-year term. It does not create a separate database.
How much can RDS Reserved Instances save?
AWS advertises savings of up to 69% versus On-Demand rates for steady-state workloads. Actual savings depend on the engine, class, Region, term, payment option, and current offering.
Which RDS engines support size flexibility?
AWS lists Db2, MariaDB, MySQL, Oracle BYOL, and PostgreSQL. SQL Server and Oracle License Included are excluded. Aurora uses separate reserved-instance rules.
Can Database Savings Plans cover Oracle and SQL Server?
Eligible RDS usage is included regardless of engine. For SQL Server, the plan discounts the instance price, while Windows Server and SQL Server license charges remain On-Demand.
Should I choose an RDS RI or a Database Savings Plan?
Use RDS RIs for stable, well-understood baselines where deeper discounts justify specificity. Use Database Savings Plans when one-year commitment flexibility across eligible database usage matters more.
Share
Facebook
X
LinkedIn
Reddit
