For R8i and M8i instances, AWS advertises up to 53% savings versus On-Demand pricing with 1-year and 3-year Oracle Reserved Instances.
BYOL vs. License Included economics
Amazon RDS for Oracle supports two licensing models. Under BYOL, you use eligible existing Oracle licenses and maintain the required Software Update License and Support. BYOL supports Oracle Standard Edition 2 and Enterprise Edition. License Included is available for Standard Edition 2 and includes the Oracle software license in the AWS service price.Oracle BYOL Reserved Instances support size flexibility. AWS can apply the RI benefit across different sizes within the same instance class type using normalized units.
Oracle License Included RIs do not receive that benefit. AWS Reserved DB Instance guidance confirms that size flexibility applies to Oracle BYOL but not Oracle License Included.
If the running DB instance changes outside the RI specifications, the reservation discount may stop matching even though the RI continues billing.
Size flexibility is a billing benefit, not an Oracle licensing entitlement. A resize can change license requirements, so validate your Oracle rights before changing instance configuration.
For broader commitment mechanics, see the RDS Reserved Instances pricing guide. For licensing economics, see our Oracle BYOL cost guide.
What changed for Oracle RIs?
In June 2025, RDS for Oracle added R7i and M7i Reserved Instances with savings advertised up to 46% compared with On-Demand pricing.On July 31, 2026, AWS added 1-year and 3-year R8i and M8i Reserved Instances with savings advertised up to 53%. RI benefits apply to Single-AZ and Multi-AZ configurations within the same database instance class type, and BYOL size flexibility applies within the family.
R8i and M8i Oracle RIs are available where those instance types are supported, except in South America (São Paulo).
If you plan to migrate families, migrate and right-size before committing. An RI should be purchased against the configuration you expect to keep, not the configuration you already plan to replace.
Oracle RDS BYOL Reserved Instance pricing
An Oracle RDS Reserved Instance discounts eligible hourly DB instance usage. It does not discount every line item on the database bill.According to AWS Reserved DB Instance billing guidance, storage, backups, and I/O are not discounted by the RI. Other separately billed charges, including data transfer where applicable, also need to be included in your total-cost model.
For a deeper cost breakdown, see our RDS storage cost guide.
For BYOL, Oracle licensing and support remain separate from AWS compute charges. AWS states that Multi-AZ BYOL deployments are expected to require twice as many licenses as the corresponding Single-AZ deployment because the standby DB instance must also be considered. Review the AWS Oracle licensing guidance and your Oracle agreement before making the final licensing decision.
This can materially change total cost. Do not treat the AWS compute discount as the complete Oracle savings case.
Include these costs in your comparison
Before comparing BYOL, License Included, an RI, or a Database Savings Plan, include:Oracle edition: SE2 or Enterprise Edition
Existing Oracle license entitlement
Active Software Update License and Support
Required license quantity for Single-AZ or Multi-AZ
Separately licensed Oracle options or features
RDS instance compute
Storage and provisioned IOPS
Backup and snapshot storage
Data transfer
Expected family, size, Region, and engine changes
Which payment option should you choose?
RDS Reserved Instances use three payment structures.| Payment option | Term | Cash-flow profile | Best fit |
|---|---|---|---|
| No Upfront | 1 year only | No upfront payment; discounted hourly billing for every hour of the 1-year term, regardless of usage | Stable 12-month baseline with limited capital outlay |
| Partial Upfront | 1 or 3 years | Part paid upfront; remaining discounted hourly charge applies for every hour of the 1- or 3-year term, regardless of usage | Stable workloads where cash preservation still matters |
| All Upfront | 1 or 3 years | Full reservation cost paid at purchase | Highly stable workloads where maximum available rate reduction justifies the outlay |
Not every RDS instance class supports every offering type. AWS notes that some instance classes might not offer No Upfront. Check the actual Reserved Instance offerings in the RDS console before budgeting or purchasing.
For term selection, see our 1-year vs. 3-year RDS RI guide.
Oracle RI buying decision framework
Use this sequence before purchasing.| Question | If yes | If no |
|---|---|---|
| Do you already have appropriate Oracle licenses and support? | Evaluate BYOL | Evaluate License Included SE2 |
| Is the target family stable for at least 12 months? | Continue | Compare a Database Savings Plan or stay On-Demand until migration or right-sizing is complete |
| Could the instance size change? | BYOL flexibility reduces RI matching risk | LI may still fit if exact size is stable |
| Is usage predictable for three years? | Compare 3-year Partial and All Upfront | Prefer a 1-year option |
| Could the engine, family, Region, or service change? | Compare a Database Savings Plan | An RI may fit |
Illustrative savings calculation
Assume eligible R8i or M8i Oracle DB instance usage would cost $10,000 at On-Demand rates over a comparison period, and the exact RI configuration qualified for AWS’s advertised 53% maximum savings.RI, DSP, or On-Demand?
Choose an Oracle BYOL RI when the database has a stable engine, family, Region, and long-running compute baseline, and you want to pursue the deeper RI rate available for that configuration.Choose a Database Savings Plan when eligible database spend is predictable but the underlying engine, instance family, deployment option, Region, or database service may change. AWS confirms that RDS for Oracle is eligible for Database Savings Plans, with savings up to 20% over a one-year commitment.
The broader Database Savings Plans program advertises savings up to 35% across eligible database services and deployment models.
Stay On-Demand when the workload is temporary, actively resizing, approaching a migration, or too uncertain to support a reliable hourly commitment.
For broader DSP coverage and eligibility, see our AWS Database Savings Plans guide.
Database Savings Plans vs. Oracle RIs
Database Savings Plans support eligible Amazon RDS for Oracle usage.| Factor | Oracle RDS Reserved Instance | Database Savings Plan |
|---|---|---|
| Term | 1 or 3 years | 1 year |
| Oracle savings ceiling discussed here | R8i/M8i advertised up to 53% | RDS for Oracle advertised up to 20% |
| Commitment basis | RI matching specifications | Consistent eligible database spend in $/hour |
| Configuration flexibility | Narrower | Broader across eligible engines, families, sizes, deployment options, Regions, and services |
| Upfront choices | No, Partial, or All Upfront depending on offering | No upfront |
| Same-workload stacking | N/A | Cannot combine with an RDS RI on the same workload |
AWS also confirms that a Database Savings Plan and an RDS Reserved Instance cannot be combined on the same workload.
For a stable Oracle fleet, compare the actual RI offer with the DSP rate rather than assuming one commitment product is always cheaper.
Check support before you commit
Oracle version lifecycle still matters even though RDS for Oracle does not use the same RDS Extended Support model documented for MySQL and PostgreSQL.Current AWS RDS for Oracle upgrade guidance lists December 31, 2029 as the expected upgrade date for Oracle Database 19c with BYOL Premier Support, December 31, 2032 with BYOL Extended Support at extra cost or an Unlimited License Agreement, and December 31, 2029 for License Included.
Oracle Database 21c has an expected upgrade date of July 31, 2027 and is not available for Extended Support.
Before a multi-year RI purchase, test any required target version and confirm post-upgrade instance requirements. A three-year commitment made immediately before a major database change can reduce the value of the discount
How to buy Oracle Reserved Instances
Cloud cost optimization isn’t a project with an end date usage shifts, workloads migrate, and pricing models change, so today’s commitment decisions need revisiting continuously, not quarterly.
The sequence still applies: stop idle spend, rightsize against real usage data, then commit against your confirmed baseline. Skipping straight to commitments is the most common reason organizations end up with stranded reservations and shrinking margins.
Sustained savings come from treating this as an ongoing discipline, clear ownership, automated execution, and a backstop against forecast error, not a quarterly finance exercise. The fastest way to start is building your commitment baseline from real usage data before your next billing cycle closes.
Confirm whether the database is BYOL or License Included.
Validate Oracle edition, support status, and license quantity.
Account for Multi-AZ licensing if applicable.
Complete planned family migrations and major right-sizing first.
Check the RDS console for current RI offerings in the target Region.
Compare a DSP if eligible database configuration or service may change.
Commit only the stable baseline you expect to use for the full term.
How Usage.ai helps manage commitment risk
With our Flex Commitments, teams can pursue up to 57% savings available with eligible three-year AWS compute Reserved Instances, with none of the long-term commitment risk.We manage eligible commitments around actual usage and charge based on the savings we deliver. Commitments we optimize, manage, generate savings from, and protect with cashback are covered under the Flex Commitment Program eligibility rules.
If a Flex Commitment costs more than equivalent On-Demand usage, we provide cashback to help cover that difference, subject to current program eligibility and terms.
This helps teams pursue deeper commitment-based savings while reducing the financial risk of workloads changing during the commitment period.
See how our Flex Commitments help manage eligible AWS commitments while reducing long-term commitment exposure.
Frequently asked questions
Do Oracle BYOL RIs support size flexibility?
Yes. AWS confirms that RDS for Oracle BYOL Reserved Instances support size flexibility within the same instance class type using normalized units. The benefit can apply across different sizes, but it does not remove your obligation to maintain the correct Oracle license entitlement.
Do Oracle License Included RIs support size flexibility?
No. AWS excludes RDS for Oracle License Included from RI size flexibility. If the running instance changes outside the RI specifications, the discount might no longer match.
Can I cancel an Oracle RDS Reserved Instance?
No. Purchase only after confirming the Region, engine, licensing model, instance requirements, term, and expected baseline usage.
Can a Database Savings Plan cover RDS for Oracle?
Yes. The Amazon RDS for Oracle FAQ states that Database Savings Plans can reduce eligible RDS for Oracle costs by up to 20% in exchange for a consistent one-year usage commitment.
Does Multi-AZ Oracle BYOL require more licenses?
Yes. AWS states that Multi-AZ BYOL deployments are expected to require twice as many licenses as the corresponding Single-AZ deployment to account for the standby DB instance. Confirm the precise entitlement under your Oracle agreement before deployment.