Oracle counts AWS under an authorized cloud policy that ignores the core factor table and turns vCPUs into licenses. This guide shows how BYOL works on EC2 and RDS, where the math bites, and how to keep the count honest.
Bringing your own Oracle Database license to AWS looks simple until you read how Oracle counts cores in a cloud it calls authorized but does not control. This guide shows how BYOL works on EC2 and RDS, where the vCPU math bites, and the buyer side moves that keep the count honest.
Moving Oracle to AWS does not move the licensing problem. It changes the rules you count under.
Oracle publishes a separate policy for what it calls authorized cloud environments. Get that policy and the AWS instance model right together, and BYOL works. Get either wrong and the cloud bill carries a hidden license bill on top.
BYOL means you apply Oracle licenses you already own to instances you run on AWS, under Oracle's authorized cloud policy rather than its on premises rules.
Oracle counts cores in AWS and Azure under its policy for licensing Oracle software in authorized cloud environments, which defines the vCPU to license conversion and replaces the on premises core factor table.
With hyper threading enabled, Oracle counts two AWS vCPUs as one Processor license. With hyper threading off, it counts one vCPU as one license. Instance shape, not raw core count, drives the number.
On premises, the core factor table can discount Intel cores to a fraction of a license. In authorized cloud that table does not apply, so the cloud count can be higher per core than many buyers expect, measured against the licensing basics Oracle publishes.
EC2 and RDS are different BYOL models. The choice changes who controls the count and how you license it.
On EC2 you run and patch the database yourself. You control instance shape and can use Dedicated Hosts to pin the physical footprint, which is the main way to manage the license count on the platform.
Amazon RDS for Oracle supports BYOL on a managed service. AWS handles patching and backups, and you license the underlying vCPUs of the instance class under Oracle's cloud policy.
RDS also offers a License Included model where the Oracle license is bundled into the hourly rate. For smaller, variable, or short lived databases this is frequently cheaper than holding perpetual BYOL entitlements.
Oracle on AWS deployment models compared
| Model | Who manages | Best fit |
|---|---|---|
| EC2 BYOL | You | Full control, Dedicated Hosts |
| RDS BYOL | AWS managed | Owned licenses, less admin |
| RDS License Included | AWS managed | Small or bursty workloads |
| Standard Edition 2 | Either | Socket limited workloads |
The count on AWS is set by instance choice. Right size the instance and you right size the license bill.
Match the instance vCPU count to the real workload, not to a generous performance buffer. Every excess vCPU above the workload need is a Processor license under the cloud policy.
EC2 Dedicated Hosts let you see and pin the physical sockets and cores, which supports socket based Standard Edition 2 licensing and gives a defensible count for an audit.
The standard advice from many cloud and reseller teams is that BYOL is always cheaper than License Included because you reuse licenses you already paid for. We disagree. In roughly 6 of 10 AWS Oracle reviews we have run, License Included on RDS was cheaper once we accounted for the support stream on idle BYOL entitlements and the oversized instances buyers chose for headroom. The buyer side move is to model both options against the real workload shape, count the vCPUs under the cloud policy honestly, and treat owned licenses as a sunk cost to redeploy elsewhere if License Included wins on the workload in front of you.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On AWS the Oracle decision is made in the instance picker, not the contract. The vCPU shape you choose is the license count you pay.
Authorized cloud removes some on premises questions and adds new ones around shapes, regions, and failover.
An audit on AWS turns on instance shapes and uptime, not physical servers. Keep records of instance classes, hyper threading state, and run times to defend the count under Oracle's cloud policy.
Standby and failover instances still attract license treatment under Oracle policy, even when idle. Assess each one rather than assuming a cloud standby is free, and confirm against Oracle support policy terms.
Just as on premises, options enabled on a cloud image are licensable whether or not they are used. Build AWS Oracle images with only the options the workload needs.
On AWS Oracle counts cores under its authorized cloud policy, not the on premises core factor table. With hyper threading enabled it counts two vCPUs as one Processor license, and with hyper threading off it counts one vCPU as one license, so the instance shape drives the number.
No. The core factor table that can discount Intel cores on premises does not apply in authorized public cloud. Oracle uses a flat vCPU to license conversion instead, which means the per core cost on AWS can be higher than buyers expect when they assume on premises math.
Not always. In our reviews License Included on Amazon RDS was cheaper for smaller and bursty databases once the support stream on idle BYOL entitlements and oversized instances was counted. Model both options against the real workload shape before assuming BYOL wins.
Yes. Standard Edition 2 can run on AWS, and its socket based limits make Dedicated Hosts useful, because they expose the physical sockets and cores. SE2 suits socket limited workloads and avoids the separately licensed options that Enterprise Edition bundles.
On EC2 you manage and patch the database yourself and control instance shape and Dedicated Hosts. On Amazon RDS for Oracle, AWS manages patching and backups while you license the instance vCPUs. EC2 gives more control, RDS reduces administration.
Usually yes, even when idle. Standby and failover instances attract license treatment under Oracle policy, so each one should be assessed against the configuration and failover use rather than assumed to be free because it sits in the cloud unused.
Right size instances to the real workload, because every excess vCPU above the need is a Processor license under the cloud policy. Use Dedicated Hosts for socket based Standard Edition 2, model License Included for small workloads, and build images with only needed options.
An AWS audit turns on instance shapes, hyper threading state, and uptime rather than physical servers. Keep records of instance classes and run times to defend the count under the authorized cloud policy, and ensure only used options are enabled on each image.
Yes. Oracle lists AWS, alongside Azure, as an authorized cloud environment with its own counting policy. That policy defines the vCPU to license conversion and replaces the on premises core factor table, so it is the document to count against, not the price list footnotes.
It usually pays for itself. The license count is fixed by instance choices made for performance, often with no view of the cost they create, and Oracle frames cloud policy to protect revenue. Independent buyer side advisory builds the honest vCPU count and the BYOL versus License Included model.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement and IT asset leaders running the next Oracle renewal or ULA cycle.
BYOL to AWS is not a discount by default. It is a counting exercise, and the buyer who counts vCPUs under the cloud policy first is the one who stays in control of the bill.
