.png)
AWS
Microsoft Azure
Google Cloud
Key takeaways
1
RDS MySQL Reserved Instances can reduce eligible database instance costs by up to 69%, but actual savings depend on the Region, instance family, term, and payment option.
2
Choose and rightsize the instance family before committing. Also verify the MySQL version because Extended Support charges are separate from RI discounts.
3
For stable workloads, RDS RIs can offer deeper savings. If your database configuration may change, compare Database Savings Plans for broader flexibility.
RDS MySQL Reserved Instances pricing can reduce eligible DB instance costs substantially compared with On-Demand pricing. AWS publishes RDS Reserved Instance savings of up to 69% for steady-state usage, but that figure is a maximum rather than a guaranteed workload-level discount.
The bigger decision is not simply whether to reserve. You also need to select the right generation, size the workload correctly, confirm the engine is not creating Extended Support charges, and determine whether an RI or Database Savings Plan better fits the expected stability of your fleet.
M8g and R8g use Graviton4. AWS reported up to 40% higher performance and 29% better price-performance for Graviton4 RDS instances compared with equivalent Graviton3 instances when it announced R8g and M8g Reserved Instance availability.
AWS now also documents db.m9g, based on Graviton5, for qualifying RDS for MySQL 8.0 and 8.4 versions. Check the current supported DB engines and instance classes before choosing a family.
The bigger decision is not simply whether to reserve. You also need to select the right generation, size the workload correctly, confirm the engine is not creating Extended Support charges, and determine whether an RI or Database Savings Plan better fits the expected stability of your fleet.
What Graviton generation fits MySQL?
AWS offers several Graviton families for RDS MySQL. T4g is burstable and best suited to lighter or variable CPU workloads. M7g provides Graviton3 general-purpose compute, while R7g provides a memory-optimized profile.M8g and R8g use Graviton4. AWS reported up to 40% higher performance and 29% better price-performance for Graviton4 RDS instances compared with equivalent Graviton3 instances when it announced R8g and M8g Reserved Instance availability.
AWS now also documents db.m9g, based on Graviton5, for qualifying RDS for MySQL 8.0 and 8.4 versions. Check the current supported DB engines and instance classes before choosing a family.
| Instance family | Profile | Best use case | RI availability |
|---|---|---|---|
| db.t4g | Graviton2, burstable | Dev/test, low traffic | 1- and 3-year |
| db.m7g | Graviton3, general purpose | Balanced production | 1- and 3-year |
| db.r7g | Graviton3, memory optimized | Large MySQL buffer pools | 1- and 3-year |
| db.m8g | Graviton4, general purpose | Graviton4 balanced workloads | 1-year; verify current offerings |
| db.m9g | Graviton5, general purpose | Latest-generation supported MySQL 8.0 and 8.4 workloads | Verify current offerings |
| db.r8g | Graviton4, memory optimized | Memory-heavy workloads | 1-year; verify current offerings |
| db.r6i/db.m6i | x86 | x86 compatibility requirements | Verify current offerings |
At launch, AWS announced one-year RIs for R8g and M8g in Regions where the corresponding Graviton4 RDS instances had On-Demand pricing. Always verify the current offering before purchasing.
Covered: eligible matching DB instance usage.
Not covered: storage, provisioned I/O or throughput, backups, data transfer, RDS Extended Support, and T4g surplus CPU credit charges.
The RDS for MySQL pricing documentation separates these additional charges from DB instance pricing, so your effective total-bill savings can be lower than the RI percentage shown for compute.
Do not rely on a copied point-in-time hourly rate when making a purchase. RDS MySQL Reserved Instances pricing should be checked against the actual offering available when you are ready to commit.
Size flexibility does not make reservations portable across instance families. An R8g reservation does not automatically cover R7g, M8g, or M9g usage.
That means a family migration can leave an existing RI without sufficient matching usage even if the underlying database workload still exists. AWS explains these matching rules in its size-flexible Reserved DB Instance documentation.
For a deeper walkthrough, see our RDS MySQL RI size flexibility guide.
What an RDS MySQL RI covers
An RDS RI discounts eligible DB instance usage that matches the reservation. It does not discount every component of the RDS bill.Covered: eligible matching DB instance usage.
Not covered: storage, provisioned I/O or throughput, backups, data transfer, RDS Extended Support, and T4g surplus CPU credit charges.
The RDS for MySQL pricing documentation separates these additional charges from DB instance pricing, so your effective total-bill savings can be lower than the RI percentage shown for compute.
RDS MySQL Reserved Instances pricing
AWS offers No Upfront, Partial Upfront, and All Upfront payment structures across eligible RDS RI offerings. The exact configuration available depends on the selected instance family, Region, deployment, and term.Do not rely on a copied point-in-time hourly rate when making a purchase. RDS MySQL Reserved Instances pricing should be checked against the actual offering available when you are ready to commit.
How to verify your exact RI offer
- Open the Amazon RDS console and go to Reserved instances.
- Filter by Region, MySQL engine, DB instance class, Single-AZ or Multi-AZ deployment, term, and payment option.
- Record the Reserved DB Instance Offering ID, FixedPrice, UsagePrice, configuration, source, and date checked.
- For Partial Upfront or All Upfront offerings, calculate the effective hourly rate as (FixedPrice ÷ term hours) + UsagePrice. Use 8,760 hours for one year and 26,280 hours for three years.
- For repeatable validation, use DescribeReservedDBInstancesOfferings through the AWS API or CLI.
How MySQL RI size flexibility works
RDS MySQL Reserved Instances support size flexibility within eligible configurations using normalization units. This can allow a reservation to cover different DB instance sizes within the same family when the normalized usage matches.Size flexibility does not make reservations portable across instance families. An R8g reservation does not automatically cover R7g, M8g, or M9g usage.
That means a family migration can leave an existing RI without sufficient matching usage even if the underlying database workload still exists. AWS explains these matching rules in its size-flexible Reserved DB Instance documentation.
For a deeper walkthrough, see our RDS MySQL RI size flexibility guide.
How to size a MySQL RI
Before committing, review at least 30 days of CPUUtilization, FreeableMemory, BufferCacheHitRatio, DatabaseConnections, and storage I/O.Rightsize first, then benchmark the intended family under production-representative load. For a long-term commitment, a short On-Demand test is inexpensive compared with reserving more capacity than the workload needs.
The T4g CPU credit trap
T4g instances use a burstable CPU model. When sustained CPU usage exceeds the available baseline and credits, surplus CPU charges can be incurred separately from the RI discount.If CPU demand regularly exceeds the burstable baseline, evaluate a non-burstable M or R family before reserving T4g. The instance discount and CPU-credit charges should be evaluated separately when estimating total savings.
How MySQL Extended Support affects RIs
MySQL 5.7 has been in Year 3 RDS Extended Support pricing since March 1, 2026. Extended Support is charged per vCPU-hour separately from normal RDS instance charges and is not reduced by the RI discount.RDS standard support for MySQL 8.0 ended on July 31, 2026, with Extended Support beginning August 1, 2026, according to the AWS RDS for MySQL version support schedule.
If you still run MySQL 5.7 or 8.0, evaluate upgrading to MySQL 8.4 before making a new long-term commitment. Reserving first and upgrading later can leave you paying both the committed RI cost and the Extended Support surcharge.
For a deeper breakdown, see our RDS Extended Support pricing guide.
RI or Database Savings Plan?
RDS RIs and Database Savings Plans address predictable database spend differently. Their benefits do not stack on the same eligible usage.| Fleet condition | RDS RI | Database Savings Plan |
|---|---|---|
| Stable Region, engine, and family | Strong fit, higher maximum discount | Viable with more flexibility |
| Frequent family or Region changes | Higher mismatch risk | More flexible |
| Predictable spend across eligible database services | Narrower matching | Strong fit |
| MySQL 5.7 or 8.0 | Upgrade first | Upgrade first |
AWS Database Savings Plans provide up to 35% savings with a one-year No Upfront commitment and can apply across supported database services, Regions, instance families, sizes, and other eligible dimensions.
For stable configurations, compare the available RI directly with the Database Savings Plan rate. If your database architecture is likely to change, the broader flexibility of a Database Savings Plan may justify its lower maximum savings ceiling.
For stable configurations, compare the available RI directly with the Database Savings Plan rate. If your database architecture is likely to change, the broader flexibility of a Database Savings Plan may justify its lower maximum savings ceiling.
Commitment decision checklist
Before purchasing an RDS MySQL commitment, confirm:Engine version and Extended Support status
AWS Region
Single-AZ or Multi-AZ deployment
Target instance family and generation
Expected baseline utilization
Rightsizing and upgrade roadmap
Current RI term and payment options
Whether a Database Savings Plan fits better
Current AWS offering ID and price
What the savings look like
Example fleet: four db.r8g.large MySQL instances running continuously in a stable configuration.Because current RI pricing is offering-specific, calculate the opportunity using the AWS rate retrieved at the time of review:
Annual On-Demand cost
=
4
×
current On-Demand hourly rate
×
8,760
Annual RI cost
=
4
×
current effective RI hourly rate
×
8,760
Annual savings
=
On-Demand annual cost
−
RI annual cost
For upfront offerings.
Effective hourly RI rate
=
(FixedPrice ÷ term hours)
+
UsagePrice
Record the Region, deployment type, engine, class, term, payment option, offering ID, checked date, and source alongside the result.
Verify the exact AWS offering first, then compare it with a Database Savings Plan and the value of maintaining flexibility.
Teams can achieve up to 50% savings on covered cloud spend, on average. Our fee is based on realized savings, and eligible Flex Commitments include cashback protection when applicable under current program terms.
Cashback protection applies only to eligible Flex Commitments that we optimize, manage, generate savings from, and bill under the program. It does not automatically apply to existing customer-owned RDS Reserved Instances or commitments outside the Flex Commitment Program. Review the current Flex Commitment eligibility requirements before applying the program to an AWS commitment opportunity.
AWS still controls the underlying commitment products, pricing, eligibility, and billing. We manage the optimization layer around eligible commitments, helping teams balance savings with flexibility as workloads change.
Make the final RDS MySQL commitment decision
RDS MySQL Reserved Instances pricing is most valuable when the workload, engine, Region, and instance family are stable enough to match the commitment throughout its term.Verify the exact AWS offering first, then compare it with a Database Savings Plan and the value of maintaining flexibility.
How Does Usage.ai Automate MySQL Reserved Instance Purchasing?
The RDS RI savings discussed in this guide are AWS pricing benefits. At Usage.ai, we focus on reducing the risk and management burden around cloud commitments. Through our Flex Insured Commitment Program, eligible workloads can access commitment-based savings without taking on the same long-term commitment exposure.Teams can achieve up to 50% savings on covered cloud spend, on average. Our fee is based on realized savings, and eligible Flex Commitments include cashback protection when applicable under current program terms.
Cashback protection applies only to eligible Flex Commitments that we optimize, manage, generate savings from, and bill under the program. It does not automatically apply to existing customer-owned RDS Reserved Instances or commitments outside the Flex Commitment Program. Review the current Flex Commitment eligibility requirements before applying the program to an AWS commitment opportunity.
AWS still controls the underlying commitment products, pricing, eligibility, and billing. We manage the optimization layer around eligible commitments, helping teams balance savings with flexibility as workloads change.
Frequently asked questions
What discount can RDS Reserved Instances provide?
AWS states that RDS Reserved Instances can save up to 69% compared with On-Demand pricing in steady state. Actual savings depend on the configuration and available offering.
Can an R8g RI cover R7g usage?
No. Size flexibility does not make an RI portable across different instance families.
Does MySQL 8.0 incur Extended Support charges?
Yes. RDS standard support for MySQL 8.0 ended July 31, 2026, and Extended Support began August 1, 2026.
Should I upgrade before buying an RI?
If you run MySQL 5.7 or 8.0, evaluate upgrading to a supported version such as MySQL 8.4 before committing.
When should I consider Database Savings Plans?
Consider them when predictable eligible database usage may move across supported Regions, services, families, or sizes and flexibility matters more than the higher RDS RI savings ceiling.
Share
Facebook
X
LinkedIn
Reddit
