.png)
Oracle is the most expensive engine on Amazon RDS. The License Included SE2 hourly rate on a db.r6i.large is approximately $0.70/hr — nearly three times the cost of the same instance running MySQL or PostgreSQL. For BYOL, the AWS compute rate is approximately $0.25/hr on the same instance, with Oracle license costs managed separately through your own agreement with Oracle.
Reserved Instances reduce the AWS compute component of that rate by 33-57% depending on the term and payment option. For a single db.r6i.xlarge BYOL instance, a 1-year No Upfront RI saves approximately $1,460/year. A 3-year RI on the same instance saves approximately $3,100-4,200 depending on payment option. Across a production fleet of 10 Oracle instances, those savings compound into the range of a full-time engineer’s annual cost.
Before you purchase any Oracle RI, two questions determine which product you should buy and whether a bad purchase creates multi-year waste: is your instance BYOL or License Included, and does your workload have any flexibility in instance sizing? The answers produce dramatically different optimal RI strategies.
See exactly what you’re overpaying in under 60 seconds. Try the Calculator for free →
Oracle BYOL vs License Included: The RI Purchasing Fork
The RI mechanics for Oracle differ by licensing model in one critical way that every guide either gets wrong or omits entirely.
Oracle BYOL Reserved Instances are size-flexible. A db.r6i.xlarge BYOL RI (8 normalization units) can cover 2x db.r6i.large BYOL instances (4 units each) automatically. It can also cover 50% of a db.r6i.2xlarge (16 units) if that is what is running. This size flexibility applies within the same instance family and generation — an r6i RI covers only r6i instances, not r7i or r8g. Source: AWS official announcement June 20, 2025 (aws.amazon.com/about-aws/whats-new/2025/06/amazon-rds-oracle-reserved-instances-r7i-m7i-instances): ‘Amazon RDS for Oracle Reserved Instances also provide size flexibility for the Oracle database engine under the Bring Your Own License (BYOL) licensing model.’
Oracle License Included Reserved Instances are NOT size-flexible. An SE2 LI RI purchased for a db.r6i.xlarge covers only db.r6i.xlarge SE2 LI instances. If you resize the instance to db.r6i.large, the RI no longer applies. If you resize to db.r6i.2xlarge, the RI no longer applies. The SE2 LI RI is fully locked to the exact instance family, size, region, and deployment type specified at purchase.
The AI Overview for ‘rds oracle reserved instance byol pricing’ states: ‘RDS for Oracle RIs do not support size flexibility.’ This is incorrect for Oracle BYOL. Size flexibility is confirmed for Oracle BYOL in the AWS official announcement from June 2025. The incorrect claim refers to Oracle License Included, not BYOL. The distinction matters significantly for purchasing strategy: BYOL buyers should purchase RIs at the smallest size in the target family; LI buyers must purchase at the exact current instance size. Source: AWS official announcement June 20, 2025.
Also read: RDS Reserved Instances: Complete Guide — all enginesÂ
Verified Oracle RI Pricing (US East, May 2026)
All rates from Vantage.sh (AWS API) and AWS official pricing. Oracle BYOL rates are compute-only — Oracle license costs are external. Verify at aws.amazon.com/rds/oracle/pricing — rates change.
| Instance (BYOL, Single-AZ) | On-Demand/hr | 1-yr No Upfront | 1-yr Saving | 3-yr All Upfront | 3-yr Saving |
| db.r6i.large (2 vCPU, 16 GB) | $0.250 | ~$0.168/hr | ~33% | ~$0.108/hr | ~57% |
| db.r6i.xlarge (4 vCPU, 32 GB) | $0.500 | ~$0.336/hr | ~33% | ~$0.215/hr | ~57% |
| db.r6i.2xlarge (8 vCPU, 64 GB) | $1.000 | ~$0.672/hr | ~33% | ~$0.430/hr | ~57% |
| db.r8g.xlarge (4 vCPU, 32 GB) | $0.478 | ~$0.320/hr | ~33% | ~$0.200/hr | ~58% |
| db.r6i.large SE2 LI | ~$0.700 | ~$0.469/hr | ~33% | ~$0.301/hr | ~57% |
| db.r6i.xlarge SE2 LI | ~$0.952 | ~$0.638/hr | ~33% | ~$0.408/hr | ~57% |
Sources: BYOL rates from Vantage.sh (AWS API, May 2026). SE2 LI rates from oneuptime.com (February 2026) and AWS pricing page. RI discount percentages approximate, consistent with 33% at 1-yr No Upfront and 57% at 3-yr All Upfront across r6i family (consistent with r8g MySQL verified rates from prior research). 3-yr No Upfront is not available for any RDS engine — minimum is Partial Upfront. Verify all rates at aws.amazon.com/rds/oracle/pricing — rates change.
Annual savings per instance at 1-year No Upfront: db.r6i.large BYOL saves approximately ($0.250 – $0.168) x 8,760 = $718/year. db.r6i.xlarge BYOL saves approximately $1,435/year. For a fleet of 10 db.r6i.xlarge BYOL instances all on on-demand: $14,350/year in recoverable savings from a single 1-year No Upfront RI purchase across the fleet.
What the June 2025 R7i and M7i Update Means for Oracle RI Strategy
AWS launched Reserved Instance support for R7i and M7i Oracle instances on June 20, 2025. This was a significant expansion because R7i and M7i are the most current Intel-based instance generations available for Oracle on RDS, and they were previously available only at on-demand rates.
The announcement confirmed three specific points that affect Oracle RI strategy. First: up to 46% savings on R7i and M7i instances versus on-demand. Second: Reserved Instances for these instances support Multi-AZ and Single-AZ configuration flexibility — you can move between configurations within the same instance class type without voiding the reservation. Third: Oracle BYOL size flexibility is explicitly available on R7i and M7i, consistent with the broader BYOL size flexibility policy confirmed in the same announcement. Source: aws.amazon.com/about-aws/whats-new/2025/06/amazon-rds-oracle-reserved-instances-r7i-m7i-instances, June 20, 2025.
The Multi-AZ/Single-AZ flexibility is notable because standard RDS RIs for other engines do not include this across-deployment-type flexibility within a single RI. Verify whether this applies to other Oracle instance families by checking the current Oracle RI documentation at aws.amazon.com/rds/oracle/pricing before assuming cross-deployment flexibility on older instance families.
The Four Hidden Costs That Sit on Top of Your Oracle RI
A Reserved Instance covers one thing: the hourly compute rate for the DB instance class. Four cost categories apply on top of the RI compute rate and are not reduced by the reservation.
Storage: gp3 at $0.115/GB-month, io1/io2 at $0.125/GB-month plus IOPS
Storage is billed independently of the RI at standard rates. General Purpose SSD (gp3): $0.115/GB-month baseline with 3,000 IOPS and 125 MBps throughput included. Additional provisioned IOPS above baseline: $0.02/IOPS-month. Provisioned IOPS SSD (io1): $0.125/GB-month plus $0.10/IOPS-month. For a db.r6i.xlarge Oracle database with 500 GB of gp3 storage: 500 x $0.115 = $57.50/month in storage charges regardless of RI term. Source: AWS official RDS pricing page (aws.amazon.com/rds/pricing — verify, rates change).
Oracle databases are often provisioned on io1 for write-heavy OLTP workloads. A 500 GB io1 volume with 3,000 provisioned IOPS: (500 x $0.125) + (3,000 x $0.10) = $62.50 + $300 = $362.50/month in storage alone, on top of RI compute charges. The storage cost frequently exceeds the RI compute savings for write-intensive Oracle workloads.
Automated Backups: Free Within the RI Retention Window, Charged Above It
AWS provides automated backup storage free of charge up to 100% of the total provisioned database storage for RDS. A 500 GB database gets 500 GB of automated backup storage at no charge. Backup retention periods of more than 7 days tend to consume more than the free allotment for active databases with high change rates. Additional backup storage above the free tier is charged at $0.095/GB-month. Manual snapshots are charged at $0.095/GB-month from the moment they are created. Source: aws.amazon.com/rds/pricing.
The hidden cost: Oracle Enterprise Edition databases are often configured with 30-day backup retention for compliance reasons. A highly transactional Oracle EE database with 500 GB provisioned storage and a 30-day retention window may accumulate 1-3 TB of backup data at $95-285/month in backup charges. This is not reduced by the RI.
Oracle SULS: The License Cost That Continues Regardless of AWS Pricing
For Oracle BYOL instances, the Oracle Software Update License and Support (SULS) obligation continues independently of your AWS RI purchase. SULS is typically 22% of the net Oracle license fee per year. For 2 Oracle EE processor licenses at $47,500 each: annual SULS = 2 x $47,500 x 0.22 = $20,900/year. This cost does not appear on your AWS bill. It is entirely separate from your RI commitment. Teams that calculate their Oracle BYOL savings purely from the AWS RI discount often underestimate total cost by not accounting for the SULS obligation that continues regardless of whether the database runs for 5 minutes or 5 years.
Extended Support Charges
Oracle database versions past their AWS standard support end-of-life incur Extended Support charges on top of the RI rate. These charges are not reduced by reserved instances. If you purchase a 3-year Oracle BYOL RI and the engine version you are running reaches end-of-standard-support during the term, you begin paying Extended Support on top of your reserved rate.
The specific Extended Support rates for Oracle on RDS vary by version and are documented at aws.amazon.com/rds/oracle/pricing. Before purchasing any multi-year Oracle RI, verify the remaining standard support period for your Oracle version at that page. Source: AWS official RDS pricing documentation (May 2026).
The compounding risk: a 3-year Oracle BYOL RI purchased at $0.215/hr on a db.r6i.xlarge looks like a 57% saving versus on-demand. If the engine version enters Extended Support in year 2, an Extended Support surcharge applies per vCPU-hour on top of the $0.215/hr reserved rate. The RI committed you to the compute for 3 years. The Extended Support surcharge adds to the total bill regardless of the commitment. Always verify engine version support status before purchasing a 3-year RI on any Oracle database.
The Correct Oracle BYOL RI Purchasing Strategy
The size flexibility available for Oracle BYOL changes the optimal purchasing approach in three specific ways.
Buy Single-AZ RIs, Not Multi-AZ RIs
A Single-AZ Oracle BYOL RI costs approximately half of a Multi-AZ BYOL RI. Both provide RI discount coverage — a Single-AZ RI covers Single-AZ instances, and two Single-AZ RIs of the same type together provide coverage equivalent to one Multi-AZ RI at the same total committed cost. But Single-AZ RIs are more flexible: they can cover Single-AZ instances individually, and two together cover a Multi-AZ instance at the same total normalization unit count. A Multi-AZ RI covers Multi-AZ instances only.
If you convert a Multi-AZ Oracle database to Single-AZ (for example, decommissioning the standby in a non-production environment), a Multi-AZ RI no longer covers the instance. Two Single-AZ RIs continue covering two Single-AZ instances or one Multi-AZ instance interchangeably. The flexibility only runs one direction.
The R7i/M7i announcement introduced explicit Multi-AZ/Single-AZ configuration flexibility for those instance families. Verify whether this cross-deployment flexibility applies before relying on it for purchasing decisions on instance families other than R7i and M7i.
Buy at the Smallest Size in the Target Family
Because Oracle BYOL has size flexibility, purchasing RIs at the smallest size in the target family provides maximum flexibility for right-sizing changes during the term. A db.r6i.large BYOL RI (4 normalization units) can cover two of the smallest Oracle workloads, or 50% of a db.r6i.xlarge, or any fraction of a larger instance. Purchasing a db.r6i.xlarge RI and later right-sizing to a db.r6i.large results in 4 normalization units of unused coverage per hour — waste. Purchasing two db.r6i.large RIs provides coverage for any two r6i BYOL instances of db.r6i.large size, with no waste even after right-sizing.
The AWS official guidance on Oracle BYOL RIs is consistent with the general BYOL engine guidance from the June 2025 announcement: ‘the discounted rate of this Reserved Instance can automatically apply to usage of any size in the same instance family.’
Also read: RDS Extended Support Pricing: engine version cost implications (live)
Verify Engine Version Support Before Any Multi-Year Commitment
The most expensive RI mistake for Oracle workloads is purchasing a 3-year RI on an Oracle version that will reach end-of-standard-support during the term. The Extended Support surcharge is applied per vCPU-hour on top of the reserved rate, and the RI commitment continues billing until expiry. A 3-year RI on an Oracle version entering Extended Support in year 2 effectively locks in 1 year of clean savings followed by 2 years of reserved rate plus Extended Support surcharge.
Check the current Oracle version support timeline at aws.amazon.com/rds/oracle/faqs and the Extended Support pricing at aws.amazon.com/rds/oracle/pricing before committing to any RI longer than 12 months.
The Oracle LI RI Trap: Why Exact-Size Matters More Than It Sounds
Oracle License Included Reserved Instances carry a risk that is easy to overlook in the purchasing process. Because LI RIs are exact-size only, any configuration change that touches the instance class voids the RI discount entirely.
Scenarios that break an Oracle LI RI: resizing from db.r6i.xlarge to db.r6i.large (the RI is for xlarge, the running instance is now large — no match), resizing from db.r6i.xlarge to db.r6i.2xlarge (RI is for xlarge, instance is larger — no match), converting from Single-AZ to Multi-AZ (RI covers Single-AZ, instance is now Multi-AZ — no match for standard LI RIs).
In each case, the RI continues billing at the committed rate and the running instance bills at on-demand rates. You pay double for the period: the RI commitment plus the on-demand instance. This double-billing period continues until the RI expires, which can be up to 3 years for a full-term commitment.
The risk is particularly acute for Oracle SE2 LI workloads because SE2 has a 16-vCPU hard limit. Organizations approaching the SE2 capacity ceiling may need to resize upward during a 3-year RI term, voiding the RI. Before purchasing a 3-year Oracle LI RI, assess whether the workload is approaching the SE2 16-vCPU limit and whether resizing within the term is plausible. If it is, start with a 1-year LI RI rather than committing to 3 years.
Payment Options: Which to Choose for Oracle RIs
Three payment options are available for all RDS Reserved Instances, including Oracle BYOL and LI. The 3-year No Upfront option is not available for RDS — the minimum for a 3-year term is Partial Upfront.
No Upfront (1-year only): $0 paid at purchase. Discounted hourly rate billed monthly for 12 months. Approximately 33% savings on Oracle BYOL at 1-year term. Best for: first RI purchase, lower cash flow commitment, workloads where 3-year confidence is not yet established.
Partial Upfront (1-year or 3-year): lump sum at purchase plus reduced monthly charges. Approximately 35-40% savings on 1-year, 48-55% on 3-year. The 3-year Partial Upfront delivers significantly more total savings than three sequential 1-year No Upfront RIs for identical workloads. Best for: confirmed stable Oracle workloads where the upfront cash can be committed.
All Upfront (1-year or 3-year): full term cost paid at purchase. Approximately 38-42% savings on 1-year, 55-57% on 3-year. The additional saving versus Partial Upfront is modest (typically $200-500 total on an xlarge over 3 years) for the significantly larger upfront cash outlay. Best for: the most stable, highest-spend Oracle instances where maximum total cost reduction is the priority and capital is available.
Practical decision guide for Oracle: Oracle BYOL workloads that have run at stable utilization for 12+ months on a confirmed instance family and size should start with 1-year No Upfront to capture immediate savings with low commitment risk. Review utilization after 12 months. If stable, move to 3-year Partial Upfront for the next term. Oracle LI workloads: favor 1-year terms to preserve the ability to resize if the SE2 16-vCPU limit approaches.
Comparing Oracle RI Options to the Database Savings Plan
The AWS Database Savings Plan offers an alternative to RDS Reserved Instances for some Oracle workloads. The DSP covers MySQL, PostgreSQL, and Aurora but does NOT cover Oracle or SQL Server. There is no Database Savings Plan option for Oracle workloads on RDS. Source: AWS Savings Plans documentation.
For Oracle on RDS, Reserved Instances are the only AWS commitment discount product available. There is no Compute Savings Plan coverage for Oracle RDS (Compute Savings Plans cover EC2, Fargate, and Lambda compute only — not RDS). This makes Oracle RI purchasing the single available lever for reducing Oracle compute costs through AWS commitments.
The alternative to RIs for reducing Oracle costs on AWS is architectural: migrating from Oracle to an open-source engine (PostgreSQL or MySQL) eliminates the Oracle license cost entirely and enables all open-source RI and Savings Plan options. AWS provides database migration tooling (AWS Schema Conversion Tool, AWS Database Migration Service) for this purpose. The analysis of whether migration is worthwhile is outside the scope of this guide but is documented in AWS’s own migration guidance.
How Usage.ai Handles Oracle BYOL and LI RI Optimization
Usage.ai analyzes Oracle BYOL and LI instances separately because the RI purchasing rules differ between them. For BYOL instances, the platform applies the smallest-size Single-AZ RI strategy to maximize normalization unit flexibility. For LI instances, the platform treats each instance as exact-size and flags any instance that may need resizing within the proposed term — particularly instances approaching the SE2 16-vCPU limit.
See how Usage.ai optimizes Oracle BYOL and LI Reserved Instances
The platform’s 24-hour analysis refresh identifies Oracle instances where the engine version is approaching end-of-standard-support and flags these explicitly before any RI purchase recommendation. Purchasing a 3-year RI on an Oracle version entering Extended Support is a compounding cost trap — the RI savings on compute are offset or exceeded by the Extended Support surcharge over the remaining term. Usage.ai prevents this by checking version support status in every recommendation cycle.
For Oracle BYOL instances where the SULS obligation is known (from customer-provided data), the platform incorporates the external Oracle license cost into the total cost comparison between continuing Oracle BYOL versus migrating to an open-source engine. This produces a full TCO comparison rather than a compute-only RI savings estimate.
If an Oracle RI becomes underutilized — because a database is decommissioned, resized, or migrated — Usage.ai provides cashback on the unused commitment in real money. Fee: percentage of realized savings only. Zero savings means zero fee.
See exactly what you’re overpaying in under 60 seconds. Try the Calculator for free →
Frequently Asked Questions
1. Do RDS Oracle BYOL Reserved Instances support size flexibility?
Yes. Oracle BYOL Reserved Instances are size-flexible. One RI covers multiple instance sizes within the same family using normalization units. A db.r6i.xlarge BYOL RI (8 normalization units) can cover 2x db.r6i.large (4 units each) automatically. This was explicitly confirmed by AWS in the June 2025 announcement for R7i and M7i instances. The AI Overview stating ‘Oracle RIs do not support size flexibility’ is incorrect for BYOL — that statement applies only to Oracle License Included. Source: aws.amazon.com/about-aws/whats-new/2025/06/amazon-rds-oracle-reserved-instances-r7i-m7i-instances.
2. Do Oracle License Included RIs support size flexibility?
No. Oracle LI (SE2) Reserved Instances are exact-size only. A db.r6i.xlarge SE2 LI RI covers only db.r6i.xlarge SE2 LI instances. If the instance is resized to any other size, the RI no longer applies. This is the same constraint as SQL Server LI. Because LI RIs are locked, the risk of purchasing LI RIs is higher — any resize during the term voids the RI discount on the running instance while the RI commitment billing continues.
3. How much do Oracle BYOL RIs save?
Approximately 33% at 1-year No Upfront and 55-57% at 3-year All Upfront on the Oracle BYOL compute rate. On a db.r6i.xlarge BYOL running 24/7: on-demand $0.50/hr = $3,650/year. 1-year No Upfront RI at ~$0.336/hr = $2,943/year. Annual saving: approximately $707. 3-year All Upfront RI at ~$0.215/hr: $1,883/year. Annual saving: approximately $1,767. Source: Vantage.sh (AWS API) May 2026. Verify at aws.amazon.com/rds/oracle/pricing — rates change.
4. What is the 3-year No Upfront option for Oracle RDS?
It does not exist. RDS Reserved Instances — for all engines including Oracle — require at minimum Partial Upfront for a 3-year term. There is no 3-year No Upfront option for any RDS RI, unlike EC2 Savings Plans which offer a 3-year No Upfront option. Teams expecting a 3-year RDS commitment with zero cash outlay need to adjust their cash flow plan to account for the Partial Upfront requirement.
5. Does an Oracle RI cover storage, backups, or SULS?
No. Oracle Reserved Instances cover the hourly DB instance compute rate only. Storage (gp3 at $0.115/GB-month, io1 at $0.125/GB-month plus IOPS), automated backup storage above the free tier ($0.095/GB-month), and data transfer are billed separately and are not discounted by the RI. Oracle BYOL SULS (22% of net license cost per year) is an Oracle contract obligation separate from the AWS bill entirely.
6. What instance families support Oracle RIs?
All current Nitro-based RDS Oracle instance families support Reserved Instances: db.r6i, db.r7i, db.m6i, db.m7i, db.r8g, db.m8g, and others. R7i and M7i RI support was added in June 2025 with up to 46% savings. Older generation instances (db.r5, db.m5) also have RI support. The complete current list is at aws.amazon.com/rds/oracle/pricing. Verify availability in your target region as not all instance families are available in all regions.
7. Can I sell or cancel an Oracle RDS Reserved Instance?
RDS Reserved Instances can be cancelled for a prorated refund with no early termination fee currently, subject to AWS’s standard RI cancellation policy. Unlike EC2 Standard RIs, RDS Reserved Instances cannot be listed on the Reserved Instance Marketplace — there is no RDS RI Marketplace equivalent. If an Oracle RI becomes unusable (engine changed, workload decommissioned), cancellation with prorated refund is the only exit option. Verify current cancellation terms at aws.amazon.com/rds/reserved-instances — AWS may modify this policy.
8. Should I buy Oracle RI before or after migrating to a newer instance family?
Always migrate first, then buy the RI. An R6i RI does not cover R7i instances and an R8g RI does not cover R6i instances. Purchasing an RI on the current instance family and then migrating to a newer generation during the term voids the RI discount on the new instances while the old RI billing continues. Migrate to the target instance family, run for 30 days to confirm the new instance is correctly sized and stable, then purchase the RI on the new family.
