.png)
Key takeaways
1
BYOL pays only when you already hold licenses you can assign at no incremental cost. If you would need to buy Oracle licenses for the deployment, price the acquisition, support, and feature-pack costs against License Included SE2 before committing.
2
Your instance class decides your license count, because Oracle counts by vCPU on RDS. Memory-per-vCPU, processor configuration, and edition all change how many licenses a given workload consumes.
3
Under BYOL you maintain the Oracle licenses and support, and that obligation runs outside the AWS bill. SULS must stay active on every license used, and AWS License Manager is the tool AWS provides for tracking it.
If you own Oracle licenses, BYOL on Amazon RDS removes the license premium AWS bundles into the License Included rate.
For a like-for-like comparison, price the same Region, instance class, deployment type, and purchasing model in the AWS Pricing Calculator. Then add Oracle licensing and support costs that sit outside the AWS bill for BYOL, plus storage, backup, I/O, and any Reserved DB Instance commitment.
That is a starting point, not a verdict. Edition requirements, how Oracle counts licenses on your instance class, and the SULS you pay either way can all move the answer.
For a like-for-like comparison, price the same Region, instance class, deployment type, and purchasing model in the AWS Pricing Calculator. Then add Oracle licensing and support costs that sit outside the AWS bill for BYOL, plus storage, backup, I/O, and any Reserved DB Instance commitment.
The Short Answer
BYOL is the more natural fit when you already hold Oracle licenses you can assign to the deployment, or when the workload needs Enterprise Edition, which License Included does not offer on RDS. License Included SE2 is the more natural fit when you hold no licenses and SE2 covers the workload.That is a starting point, not a verdict. Edition requirements, how Oracle counts licenses on your instance class, and the SULS you pay either way can all move the answer.
BYOL or License Included? Start Here
| Your situation | Recommended model |
|---|---|
| You own perpetual Oracle licenses with active SULS | BYOL: lower AWS instance rate; manage Oracle licensing and other RDS costs separately |
| You have an active or recently certified ULA | BYOL: confirm cloud deployment rights in your ULA terms first |
| You have idle shelfware from decommissioned hardware | BYOL: redirect existing entitlements |
| You need Enterprise Edition features | BYOL only: LI does not offer EE |
| You host Oracle databases for external customers | BYOL required: LI is prohibited under AWS Service Terms 10.3.1 |
| No existing Oracle licenses, SE2 features are sufficient | License Included SE2: lower licensing-administration burden |
| Single small instance, SULS overhead exceeds savings | License Included SE2: total cost of ownership may favor LI |
Two more cases tilt toward License Included even when BYOL is possible. Overhead: for a single small instance, the effort of compliance documentation and Oracle support management can exceed the premium saved.
Support model: LI routes Oracle requests through AWS Support where you have eligible case support simpler for teams that want one support vendor.
Support model: LI routes Oracle requests through AWS Support where you have eligible case support simpler for teams that want one support vendor.
RDS Oracle BYOL vs License Included
| Dimension | License Included (LI) | Bring Your Own License (BYOL) |
|---|---|---|
| What you pay AWS | Compute + Oracle license bundled in hourly rate | Instance hourly rate; Oracle license cost is yours to manage |
| Database editions | SE2 only | SE2 and Enterprise Edition (EE) |
| Permitted use | Internal use only; no third-party hosting (AWS Service Terms 10.3.1) | Internal and hosting permitted with correct entitlements |
| Size-flexible RIs | Not available: exact size only | Available for SE2 and EE BYOL |
| Oracle Support | AWS Support handles Oracle requests with eligible case support | Your SULS entitlement; direct My Oracle Support access |
| License compliance | AWS (for the bundled license terms) | You; Oracle agreements still apply |
| Bare metal instances | Not available | Available (Sept 2025 for EE, Jan 2026 for SE2) |
| Instance rate (db.r6i.xlarge) | Check current AWS pricing for your Region and deployment type | Check current AWS pricing for your Region and deployment type; Oracle licensing is separate |
The decision is also reversible: AWS lets you change the licensing model on an existing DB instance by modifying it, and under BYOL you can migrate SE2 to EE via snapshot restore (EE cannot migrate down).
Full details are in AWS’s RDS for Oracle licensing options. If you haven’t confirmed which edition your workload needs, see our comparison of Oracle EE vs SE2 on RDS before committing.
What does not qualify:
Full details are in AWS’s RDS for Oracle licensing options. If you haven’t confirmed which edition your workload needs, see our comparison of Oracle EE vs SE2 on RDS before committing.
Do You Have Qualifying Oracle Licenses?
BYOL saves money only when you can assign qualifying licenses to the deployment at no incremental cost. Three license types qualify:- Perpetual licenses with active SULS (Software Update License and Support, backed by a valid Customer Support Identifier), the most common eligible type.
- Active or recently certified ULAs, where your agreement permits deployment on AWS, confirm the position with your Oracle contract owner. One limit under Oracle’s cloud policy: cloud deployments cannot be counted in the certification at the end of the ULA term, so plan your exit certification around on-premises usage.
- Idle shelfware from decommissioned on-premises hardware, redirected under Oracle’s cloud licensing policy conditions.
What does not qualify:
- Term (subscription) licenses, unless your contract specifically permits porting to AWS.
- Licenses without active SULS.
- Mid-term, uncertified ULAs counting rules on AWS are complex; consult your Oracle representative first.
How Oracle Counts Licenses on RDS
Oracle’s counting method depends on the edition, a distinction most guides miss.- Enterprise Edition is counted per processor: 2 vCPUs = 1 processor license when multi-threading is enabled (the default), or 1 vCPU = 1 license when it’s disabled. So a db.r6i.xlarge (4 vCPUs) requires 2 EE licenses, and a db.r6i.8xlarge (32 vCPUs) requires 16.
- Standard Edition 2 is counted per socket: every 4 vCPUs, rounded up to the nearest multiple of four, equals 1 socket, which equals 1 SE2 license. SE2 also carries a hard ceiling; it may only be licensed on cloud instances of up to 8 vCPUs.
Count by edition, not by instance.
Two counting rules, one instance.
Enterprise Edition
=
Processor licenses = vCPUs ÷ 2
(÷ 1 if multi-threading is disabled)
Standard Edition 2
=
Sockets = vCPUs ÷ 4, rounded up
(SE2 is capped at 8 vCPUs per instance)
Count before you size. The instance class you choose sets the license requirement, not the other way round.
Multi-AZ and read replicas count too. AWS is explicit: under BYOL you must license both the primary and the standby in a Multi-AZ deployment, and read replicas consume licenses at full count. Assume everything running Oracle needs a license.
Memory-optimized first. The r-family (db.r6i, db.r7i, db.r8i) provides 8 GB RAM per vCPU; the m-family provides 4 GB. For an Oracle database needing 64 GB of RAM:
Processor configuration: a BYOL-only lever. RDS for Oracle lets you customize core count and threads per core on a BYOL instance, keeping full memory while reducing active vCPUs.
AWS charges the same rate as the default configuration, the saving is entirely in Oracle licenses. It’s supported on db.r7i, db.r6i, db.m6i, the db.r5 and db.x2 families and others; the full list is in configuring processor features for RDS for Oracle.
Example: a db.r7i.2xlarge defaults to 8 vCPUs and 64 GB RAM, 4 EE licenses. Set core count to 2 with 2 threads per core and it runs 4 vCPUs at the same 64 GB, 2 EE licenses. Setting threads per core to 1 also changes Oracle’s count to 1 vCPU = 1 license under the cloud policy.
Licenses freed this way stay in your pool: assign them to another RDS instance, or retire them at renewal to reduce the SULS you pay.
To configure it:
Picking the Instance Class
Under BYOL, instance choice is license count. Two levers matter.Memory-optimized first. The r-family (db.r6i, db.r7i, db.r8i) provides 8 GB RAM per vCPU; the m-family provides 4 GB. For an Oracle database needing 64 GB of RAM:
- Db.r6i.2xlarge: 8 vCPUs → 4 EE licenses
- Db.m6i.4xlarge: 16 vCPUs → 8 EE licenses
Processor configuration: a BYOL-only lever. RDS for Oracle lets you customize core count and threads per core on a BYOL instance, keeping full memory while reducing active vCPUs.
AWS charges the same rate as the default configuration, the saving is entirely in Oracle licenses. It’s supported on db.r7i, db.r6i, db.m6i, the db.r5 and db.x2 families and others; the full list is in configuring processor features for RDS for Oracle.
Example: a db.r7i.2xlarge defaults to 8 vCPUs and 64 GB RAM, 4 EE licenses. Set core count to 2 with 2 threads per core and it runs 4 vCPUs at the same 64 GB, 2 EE licenses. Setting threads per core to 1 also changes Oracle’s count to 1 vCPU = 1 license under the cloud policy.
Licenses freed this way stay in your pool: assign them to another RDS instance, or retire them at renewal to reduce the SULS you pay.
To configure it:
1
Create or modify the instance in the console under Instance specifications → Processor features.
2
Set Core count and Threads per core.
3
Confirm the workload's CPU stays below ~80% P95 at the reduced count before committing.
Bare metal, briefly. AWS added bare metal instances for RDS Oracle EE BYOL in September 2025 and SE2 BYOL in January 2026, at 25% lower cost than equivalent virtualized instances.
They expose physical core and socket counts (most have 2 sockets; the metal-24xl variants have one) and support consolidating databases as PDBs on one instance.
Whether that reduces your Oracle license count depends on your agreement AWS says consult your licensing partner, and so do we. Details in AWS’s bare metal announcement for SE2 and our Oracle EE vs SE2 guide.
One check before any commitment: confirm your workload runs on standard RDS for Oracle, not RDS Custom for Oracle AWS has set end of support for RDS Custom for Oracle on March 31, 2027. Our RDS Custom guide covers the difference.
If you’re already paying SULS on idle or on-premises licenses, the marginal license cost of using them on RDS is essentially zero. You pay SULS regardless. The BYOL saving is then the full LI premium, the bundled Oracle license cost, before any RI discount.
If you would need to buy licenses for this deployment, include the quoted acquisition cost, support cost, required feature packs, and your expected license term in the BYOL estimate. Compare that total with the current License Included SE2 cost for an equivalent supported configuration.
Verify current RDS for Oracle pricing before committing.
License Included RIs are exact-size only: resize the instance and the RI stops applying while its billing continues, and AWS doesn’t permit post-purchase RI modification. That asymmetry is the biggest RI purchasing difference between the models BYOL commitments carry far less right-sizing risk.
For rate tables, payment options, and the full purchasing strategy, see our RDS Oracle Reserved Instance guide.
They expose physical core and socket counts (most have 2 sockets; the metal-24xl variants have one) and support consolidating databases as PDBs on one instance.
Whether that reduces your Oracle license count depends on your agreement AWS says consult your licensing partner, and so do we. Details in AWS’s bare metal announcement for SE2 and our Oracle EE vs SE2 guide.
One check before any commitment: confirm your workload runs on standard RDS for Oracle, not RDS Custom for Oracle AWS has set end of support for RDS Custom for Oracle on March 31, 2027. Our RDS Custom guide covers the difference.
What BYOL Actually Saves
Once the instance class is settled, the honest comparison includes the Oracle license cost you carry either way.If you’re already paying SULS on idle or on-premises licenses, the marginal license cost of using them on RDS is essentially zero. You pay SULS regardless. The BYOL saving is then the full LI premium, the bundled Oracle license cost, before any RI discount.
If you would need to buy licenses for this deployment, include the quoted acquisition cost, support cost, required feature packs, and your expected license term in the BYOL estimate. Compare that total with the current License Included SE2 cost for an equivalent supported configuration.
Verify current RDS for Oracle pricing before committing.
How BYOL Changes Your RI Strategy
Oracle BYOL Reserved Instances are size-flexible: one RI’s discounted rate automatically applies to any size in the same instance family via normalization units; a db.r6i.xlarge RI can cover two db.r6i.large instances.License Included RIs are exact-size only: resize the instance and the RI stops applying while its billing continues, and AWS doesn’t permit post-purchase RI modification. That asymmetry is the biggest RI purchasing difference between the models BYOL commitments carry far less right-sizing risk.
For rate tables, payment options, and the full purchasing strategy, see our RDS Oracle Reserved Instance guide.
Staying Compliant After You Deploy
Under BYOL, you must maintain the Oracle licenses, SULS, and separately licensed features required for the RDS instance class and edition you run. Keep a documented license position and review contract-specific rights with your Oracle licensing owner or qualified adviser before deploying or changing capacity.- Keep SULS active on every license used; lapsed SULS creates back-payment exposure at renewal.
- Track renewal dates in your Oracle support portal, and align instance launches with available licensed seats.
- Don’t assume licenses freed by an on-premises decommission transfer to cloud use verify the agreement terms first.
- Maintain a license position document mapping every running instance to its vCPU count, licenses consumed, and entitlement serial numbers, updated whenever instances change.
Entitlements confirmed
Perpetual licenses with active SULS, an active or certified ULA, or redirected shelfware.
License count calculated
Counted by edition against the instance class you intend to run.
Every Oracle instance counted
Standbys and replicas included, not just the primaries.
SULS active and tracked
Support must stay current on every license used, and the obligation sits outside the AWS bill.
RDS variant confirmed
Standard RDS for Oracle, not RDS Custom for Oracle, before any multi-year commitment.
How Usage.ai Optimizes Oracle BYOL RIs
Acting on that asymmetry means tracking which instances sit on which licensing model, and keeping that view current as instances are resized.We analyze BYOL and License Included instances separately, apply size-flexible purchasing to the BYOL side, and flag over-provisioned LI instances before you lock in an exact-size RI you can’t normalize out of.
With Flex Insured Commitments, teams can get the 30–40% savings of a 1-year commitment with none of the commitment risk. If a qualifying Flex Commitment ever costs more than the equivalent on-demand rate for that usage, we provide cashback protection on the difference, subject to program terms.
Our fee is a percentage of realized savings only zero savings means zero fee.
Frequently asked questions
What is RDS Oracle BYOL?
BYOL (Bring Your Own License) lets you apply existing perpetual Oracle Database licenses to Amazon RDS instances, paying AWS only for compute, storage, and the managed service. The license cost sits outside the AWS bill under your own Oracle agreement. BYOL supports SE2 and Enterprise Edition and requires active SULS.
How much cheaper is Oracle BYOL vs License Included on RDS?
The BYOL instance rate is lower because the Oracle license is not bundled into it, and that gap scales with instance size. Price the same Region, instance class, deployment type, and purchasing model in the AWS Pricing Calculator for both models, then add the Oracle licensing and support costs that sit outside the AWS bill for BYOL, plus storage, backup, and I/O. For EE, BYOL is the only option. Verify rates at aws.amazon.com/rds/oracle/pricing.
How does Oracle count licenses on AWS RDS BYOL?
By edition. Enterprise Edition: 2 vCPUs = 1 processor license with multi-threading enabled (the default), or 1 vCPU = 1 license with it disabled. Standard Edition 2: every 4 vCPUs, rounded up, equals 1 socket license, with a hard cap of 8 vCPUs per instance. Source: Oracle's Cloud Licensing Policy.
Does Multi-AZ Oracle RDS require licensing the standby?
Yes. AWS documentation states that under BYOL you must have a license for both the primary and the standby DB instance in a Multi-AZ deployment. Read replicas running Oracle consume licenses too. Budget the full deployment's license count, not just the primary.
Are size-flexible Reserved Instances available for Oracle BYOL?
Yes. BYOL RIs (SE2 and EE) are size-flexible within an instance family through normalization units, a db.r6i.xlarge RI can cover two db.r6i.large instances. License Included RIs are exact-size only, which is the key RI strategy difference between the models.
Share
Facebook
X
LinkedIn
Reddit
