Amazon RDS for Oracle is the managed Oracle Database service: AWS runs the engine, patching, backups, and high availability, and you pay per instance-hour. The pricing looks opaque because the per-hour rates sit behind a Region and deployment selector on the AWS pricing page rather than in a fixed published table, but the structure is straightforward once you see the three levers that set the number: the licensing model, the edition, and the instance class. This page is the 2026 reference for how RDS for Oracle is priced, as distinct from the one-off cost of migrating to it.
Pricing verification
The RDS for Oracle instance-hour is driven by three choices, and they compound. The licensing model sets whether the Oracle licence is bundled into the rate (License Included) or supplied by you (BYOL). The edition sets which features and which licensing paths are available. The instance class sets the compute. The deployment option (Single-AZ or Multi-AZ) then sets whether you pay for one instance or two.
The RDS for Oracle pricing levers and their effect
| Lever | Options | Effect on the instance-hour |
|---|---|---|
| Licensing model | License Included (SE2 only) / BYOL (SE2 or EE) | LI bundles the Oracle licence into the rate; BYOL pays AWS compute only and uses your entitlement |
| Edition | Standard Edition 2 / Enterprise Edition | EE adds the advanced options and has no License Included path; EE always means BYOL |
| Instance class | db.t3 / db.m5 / db.m6i / db.r5 / db.r6i and larger | Scales with vCPU and memory; the compute portion of the rate |
| Deployment | Single-AZ / Multi-AZ | Multi-AZ roughly doubles the instance cost (primary plus standby) |
License Included (LI) bundles the Oracle Database software licence into the hourly rate, so there is no separate Oracle licence to buy, track, or true-up. On RDS for Oracle, License Included is available for Standard Edition 2 (SE2) only. Bring Your Own License (BYOL) lets you apply existing Oracle entitlement and supports both Standard Edition 2 and Enterprise Edition (EE).
The choice is an entitlement question, not an instance-size question. If you do not already hold Oracle licences, License Included on SE2 is both cheaper and far simpler, and it removes the licence audit risk. If you do hold substantial Oracle entitlement, BYOL lets you put it to work and pay AWS for compute only. Enterprise Edition workloads have no License Included path at all, so they are BYOL by necessity.
The 2:1 vCPU rule applies to RDS, not just EC2
Edition decides which licensing paths are open to you and which features you get.
Amazon RDS for Oracle editions
| Edition | Licensing paths | Best for | Notes |
|---|---|---|---|
| Standard Edition 2 (SE2) | License Included or BYOL | Most production workloads, smaller estates | The only edition with a License Included option; under Oracle's cloud policy SE2 may only be licensed on instances up to eight vCPUs |
| Enterprise Edition (EE) | BYOL only | Large-scale, advanced features | Adds partitioning, advanced security, advanced compression and the EE-only options; no License Included path |
The edition rule of thumb
The instance-hour (compute, plus the Oracle licence under LI) is the bulk of an RDS for Oracle bill, but it is not the whole bill. The additional charges are:
Charges on top of the RDS for Oracle instance-hour
| Charge | Basis | Notes |
|---|---|---|
| Provisioned storage | Per GiB-month (gp3, io1/io2, or magnetic) | Sized to the database; gp3 is the cost-effective default |
| Provisioned IOPS | Per IOPS-month above baseline | Only where the workload needs guaranteed IOPS |
| Backup storage | Per GiB-month beyond free allowance | Free up to the provisioned database size; extra retention is charged |
| Snapshot export to S3 | Per GB exported | Optional; only if exporting snapshots for analytics or archival |
| Data transfer out | Per GB at standard rates | Outbound to internet or cross-Region |
For most production instances these add up to a minority of the bill; the instance-hour dominates. The practical implication: optimising RDS for Oracle cost is mostly about right-sizing the instance class, choosing the correct licensing model, and deciding Multi-AZ only where availability genuinely requires it, rather than chasing storage or backup savings.
A structural illustration (not a quote) of how the levers compound for a mid-size production database. The exact dollar figures depend on Region and current AWS rates, so confirm against the AWS Pricing Calculator; the point here is the relative weight of each lever.
How the levers compound, mid-size production Oracle on RDS (relative weighting)
| Configuration | Relative monthly cost | Driver |
|---|---|---|
| SE2 License Included, Single-AZ, mid-size class | Baseline (1.0x) | Compute plus bundled SE2 licence |
| SE2 License Included, Multi-AZ, same class | Roughly 2.0x | Standby doubles instance cost |
| SE2 BYOL, Single-AZ, same class | Below baseline on AWS spend | AWS compute only; Oracle licence paid separately via your entitlement |
| EE BYOL, Multi-AZ, same class | AWS compute x2 plus your EE entitlement | No LI path; standby doubling on top of EE licence cost |
The lesson the weighting teaches: settle the licensing model and the Multi-AZ decision first, because between them they swing both the AWS spend and the total cost of ownership the most. The instance class and the storage choices fine-tune from there. For the live per-hour rates by Region and instance class, use the AWS Pricing Calculator or the RDS for Oracle pricing page; for the one-off cost of getting your databases onto RDS in the first place, see the migration-cost page below.
Amazon RDS for Oracle pricing is opaque on the surface because the per-hour rates are served per Region behind a selector rather than as one published table, but the structure is simple: the licensing model, the edition, and the instance class set the instance-hour, and storage and backups add a minority on top. Get the licensing model and Multi-AZ decisions right, and the run-rate is predictable; get them wrong, by paying Enterprise Edition entitlement you do not use or running Multi-AZ on non-critical workloads, and you double or more the bill for no benefit. Rates and licensing terms on this page were re-derived from the Amazon RDS for Oracle pricing page and Oracle's cloud licensing policy in September 2026.
A. RDS for Oracle is priced per instance-hour, plus storage and the usual add-ons. The instance-hour depends on the instance class (the compute) and the licensing model. Under License Included, the Oracle Standard Edition 2 licence is bundled into the hourly rate; under Bring Your Own License (BYOL) you bring your own Oracle entitlement and pay only for the AWS compute. On top of the instance-hour you pay for provisioned storage per GiB-month, provisioned IOPS where used, backup storage beyond the free allowance, and data transfer out. AWS publishes the on-demand per-hour rates on its RDS for Oracle pricing page through a Region and deployment selector rather than as a fixed table, and the same rates are in the AWS Pricing Calculator, so treat any specific figure as point-in-time and Region-specific.
A. License Included (LI) bundles the Oracle licence into the hourly instance rate, so there is no separate Oracle licence to buy, track, or true-up. On RDS for Oracle, License Included is available for Standard Edition 2 (SE2) only. Bring Your Own License (BYOL) lets you apply existing Oracle entitlement and supports both Standard Edition 2 and Enterprise Edition (EE). BYOL on RDS carries the same Oracle cloud-licensing arithmetic as BYOL on EC2: Oracle's Authorized Cloud Environment policy names Amazon EC2 and Amazon RDS together and counts two vCPUs as one Oracle Processor licence where multi-threading is enabled. For most SE2 estates without existing entitlement, License Included is simpler and cheaper; Enterprise Edition workloads must use BYOL.
A. RDS for Oracle supports Standard Edition 2 (SE2) and Enterprise Edition (EE). License Included covers SE2 only. BYOL covers both SE2 and EE. Enterprise Edition adds the advanced features (partitioning, advanced security, advanced compression, and the EE-only options) and there is no License Included path for it, so EE always means BYOL. The edition choice is the largest single driver of the licence portion of the cost, and for EE it is an entitlement question rather than a rate you can read off an AWS page.
A. Multi-AZ roughly doubles the instance cost versus Single-AZ, because RDS maintains a standby in a second Availability Zone for automatic failover and you pay for both the primary and the standby. For production workloads that need high availability, Multi-AZ is the default and the doubling is the price of automatic failover. For dev/test and non-critical workloads, Single-AZ halves the instance cost. Note that RDS for Oracle Multi-AZ is RDS-managed failover, not Oracle Real Application Clusters (RAC); RAC is not available on RDS, and workloads that genuinely require it run Oracle on EC2 instead.
A. No. Oracle's policy for licensing its software in cloud computing environments names Amazon EC2 and Amazon Relational Database Service (RDS) together as Authorized Cloud Environments, and applies the same counting rule to both: two vCPUs count as one Oracle Processor licence where multi-threading of processor cores is enabled, and one vCPU counts as one Processor licence where it is not. The Oracle Processor Core Factor Table does not apply in either. For Standard Edition 2, instances of four or fewer vCPUs count as one socket, every further four vCPUs (rounded up) count as one more socket, and SE2 may only be licensed on instances up to eight vCPUs. Budget RDS BYOL on the same licence arithmetic as EC2 BYOL; the RDS advantage is managed operations, not a licensing carve-out.
A. Beyond the instance-hour, RDS for Oracle charges for: provisioned storage per GiB-month (General Purpose gp3, Provisioned IOPS io1/io2, or magnetic), any provisioned IOPS above the baseline, backup storage beyond the free allowance equal to your provisioned database size, snapshot export to S3 if used, and data transfer out at standard rates. For most production Oracle instances the storage and backup charges are a minority of the bill; the instance-hour (compute plus, under LI, licence) dominates, which is why the licensing model and instance-class choice matter most.
A. They are separate budget lines. The RDS for Oracle run-rate (instance-hour plus storage) is the ongoing destination cost after migration. The migration cost is the one-off project spend to get there: a single Oracle database under 1 TB typically costs $20,000 to $80,000 to migrate to AWS, and larger databases more, with Aurora PostgreSQL conversions costing more per database but removing Oracle licensing entirely. This page covers the run-rate pricing; the migration-cost build is on the Oracle to AWS migration cost page.
Oracle to AWS migration cost ->
The one-off cost of getting there
RDS for SQL Server pricing ->
The SQL Server equivalent
AWS DMS pricing ->
The replication tool for the migration
AWS SCT cost ->
If converting to Aurora PostgreSQL instead
AWS migration cost calculator ->
Full migration calculator
10 hidden costs ->
Licence changes in context
Updated 2 May 2026