Here is the number most organisations running Oracle Database on AWS or Azure do not know: the effective Oracle license cost for an identically sized workload is twice as high on AWS or Azure as it would be on Oracle Cloud Infrastructure. Not 10% higher. Not 30% higher. Twice as high, before you account for infrastructure costs.
This is not a consequence of Oracle raising prices. It is a consequence of how Oracle counts processor licenses in different cloud environments, a rule that changed in January 2017 and that most cloud migration decisions made since then have not fully priced in. The mechanism is specific and calculable. This article explains it precisely, shows the arithmetic for a concrete workload, and builds the TCO comparison that CFOs and database operations teams need to make an informed cloud placement decision.
On physical hardware, Oracle calculates processor licenses using the Core Factor Table. For the Intel x86 processors that run almost all enterprise workloads, the core factor is 0.5, meaning each physical core requires 0.5 Oracle processor licenses. An 8-core Intel server needs 4 Oracle processor licenses.
In the cloud, Oracle abandons the Core Factor Table. The rule that applies in AWS and Azure (environments Oracle designates as “authorized cloud environments” in its official policy document) is different:
AWS and Azure (with hyper-threading enabled, which is the default): 2 vCPUs = 1 Oracle processor license.
OCI (Oracle Cloud Infrastructure): 1 OCPU = 1 Oracle processor license. One OCPU equals one physical core with hyper-threading, which corresponds to 2 vCPUs.
The punchline is in the comparison. On AWS or Azure, 1 Oracle processor license covers 2 vCPUs. On OCI, 1 Oracle processor license covers 1 OCPU, which Oracle defines as equivalent to 2 vCPUs. So an Oracle license covers the same amount of actual processing capacity on both platforms. The difference is what happens when you compare the same physical compute.
A server with 8 physical cores, with hyper-threading, runs as 16 vCPUs. On that server:
OCI requires 8 licenses too. But here is the critical difference that the headline-level comparison misses: OCI’s licensing policy allows one Oracle license to cover 2 OCPUs, not 1 OCPU. This is Oracle’s own cloud incentive. On OCI with BYOL, one Oracle Database Enterprise Edition processor license covers 2 OCPUs, equivalent to 4 vCPUs of compute. On AWS and Azure, one license covers 2 vCPUs.
The effective ratio: OCI provides twice the compute capacity per Oracle license compared to AWS or Azure. Or equivalently: the same workload requires twice as many Oracle licenses on AWS and Azure as on OCI.
This is what Oracle themselves state: “If you’re bringing your Oracle Database licenses, you get twice as many CPUs on OCI as you do on AWS”.
Scenario: An organisation runs Oracle Database Enterprise Edition on a medium-scale production workload. On AWS, they are using two r6i.8xlarge instances. Each has 32 vCPUs.
Oracle license requirement on AWS:
Equivalent workload on OCI (using the 2-OCPU-per-license rule):
The same workload requires 32 licenses on AWS and 16 licenses on OCI. The license count differential is 16 processor licenses.
Oracle Database Enterprise Edition list price is $47,500 per processor license. Almost nobody pays list price; actual negotiated prices vary widely, but the differential between AWS and OCI stays proportional regardless of the discount applied. Using the list price for scale:
For this workload, the five-year excess license and support cost of being on AWS rather than OCI is approximately $760,000 (licenses, one-time) + $830,000 (support over 5 years) = $1,590,000, before touching infrastructure costs.
For organisations with significantly larger Oracle estates, scale these numbers proportionally. A 500 vCPU Oracle estate on AWS requires 250 licenses. The same estate on OCI requires 125 licenses under the 2-OCPU-per-license benefit. The 125-license differential at $47,500 list price is $5.9 million in licensing alone.
The 2017 policy change that eliminated the Core Factor Table for AWS and Azure was not announced loudly by Oracle. It appeared in an update to a policy document titled “Licensing Oracle Software in the Cloud Computing Environment”. Most organisations migrating to AWS or Azure in 2017 and later were not working with Oracle licensing advisors; they were working with AWS or Azure migration teams whose expertise was in infrastructure cost, not Oracle license mechanics.
The organisations most exposed to this gap are those that made their cloud platform decision based on infrastructure cost comparisons without building Oracle licensing into the TCO model. AWS and Azure are often cheaper for compute infrastructure than OCI for non-Oracle workloads. For Oracle workloads, the licensing differential reverses the infrastructure cost advantage at any meaningful scale.
The additional factor is that Oracle’s license audit function (Oracle License Management Services, or LMS) has intensified its focus on cloud deployments since 2020. An organisation that migrated Oracle to AWS in 2019, calculated license requirements incorrectly, or resized instances without recalculating license exposure, is at audit risk. Oracle LMS can demand backdated support fees at 22% per year for the period of non-compliance, in addition to the cost of missing licenses at the current list price.
A complete cost comparison requires three components: Oracle licensing, annual support fees, and cloud infrastructure costs. The infrastructure cost is the one factor where AWS or Azure may have an advantage for some configurations; the license and support differential typically dominates at scale.
| Cost component | AWS BYOL | OCI BYOL |
| Oracle license count (32 vCPUs workload) | 16 licenses | 8 licenses |
| Incremental license cost (list price $47,500) | $760,000 | $380,000 |
| Annual support at 22% | $167,200/year | $83,600/year |
| 5-year support cost | $836,000 | $418,000 |
| Total 5-year licensing + support | $1,596,000 | $798,000 |
| 5-year licensing advantage of OCI | $798,000 | — |
Note: These figures use the list price as the reference. The absolute numbers change with negotiated discounts; the differential remains proportional. Organisations paying 65% discounts off list still experience the same ratio of licenses required.
Beyond the straight license arithmetic, OCI offers Oracle Support Rewards: organisations earn $0.25 to $0.33 in credits for every $1 spent on OCI services, which can be applied against Oracle support fees. For a workload generating $500,000 per year in OCI infrastructure spend, this creates $125,000 to $165,000 per year in additional support cost offset, a benefit that does not exist on AWS or Azure.
The infrastructure cost comparison depends heavily on the specific workload, instance types, and committed use discount arrangements. For a balanced assessment:
If your organisation is running Oracle Database on AWS or Azure with BYOL, there are three immediate questions worth answering.
Are you correctly licensed? This is the baseline check. Calculate the total vCPUs across all instances running Oracle software, divide by 2, and compare to your license count. If your license count was calculated using the on-premises Core Factor Table rather than the cloud-specific 2-vCPU rule, you may be under-licensed. The discovery risk is real: Oracle LMS audit activity has increased, and cloud deployments are an explicit focus.
What is your five-year TCO if you stay? Build the model for your actual license count, actual negotiated price, actual support cost, and projected infrastructure cost. Then build the equivalent model for OCI, using the correct 2-OCPU-per-license calculation. The license differential is predictable and calculable. The infrastructure comparison requires knowing your specific workload requirements and OCI instance sizing for equivalent performance.
What is the migration cost? Moving Oracle workloads from AWS or Azure to OCI involves a migration project with its own cost and risk. The relevant question is not whether OCI is cheaper in steady state, but whether the five-year TCO advantage of OCI exceeds the migration project cost at your scale. At large Oracle estates (hundreds of licenses), the answer is almost always yes. At small estates (under 20 licenses), the migration cost may not be recoverable in a five-year window.
Pretius has delivered Oracle Cloud Infrastructure migrations for financial services organisations with specific regulatory and cost constraints, including one insurance sector migration that reduced total cloud costs by 53% within seven months of cutover. For Oracle Database workloads specifically, the migration approach involves three phases.
First, an audit of the current Oracle estate: all instances, all vCPU counts, all license assignments, and the current license calculation methodology. Organisations that have never been through an Oracle cloud licensing audit are often surprised by what this surfaces, in both directions (over-licensed and under-licensed configurations are both common).
Second, an OCI sizing and cost model: the equivalent OCI instance configuration for each workload, the correct license calculation under OCI’s rules, the infrastructure cost at OCI pricing, and a five-year TCO comparison against the current AWS or Azure cost, including license adjustment.
Third, a migration plan that accounts for the parallel running period, during which both environments run simultaneously, so that the dual-licensing cost during migration is factored into the business case rather than discovered as an unbudgeted item.
The migration from AWS or Azure to OCI for Oracle Database workloads is a technically straightforward project for organisations already running Oracle on Linux. The business case is in the licensing mathematics.
Oracle Database Enterprise Edition list price: $47,500 per processor license
Annual support cost: 22% of net license price per year
Oracle processor license requirement, AWS or Azure BYOL: 1 license per 2 vCPUs (with hyper-threading enabled, which is the default)
Oracle processor license requirement, OCI BYOL: 1 license per 2 OCPUs (equivalent to 1 license per 4 vCPUs of compute)
Effective licensing ratio AWS/Azure vs OCI: 2:1. The same compute workload requires twice as many Oracle licenses on AWS or Azure compared to OCI
Oracle Support Rewards on OCI: $0.25 to $0.33 per $1 of OCI spend, applied against Oracle support fees
Source: Oracle policy document governing cloud licensing (June 2024 version).
The cloud-specific licensing rules apply to all Oracle software products licensed by processor in authorized cloud environments, not only Oracle Database. This includes Oracle Middleware, WebLogic, and other Oracle technology products. The financial impact is largest for Oracle Database Enterprise Edition because of its $47,500 per processor list price.
If hyper-threading is disabled, Oracle’s policy counts 1 vCPU as 1 Oracle processor license, which is actually worse than the standard hyper-threaded calculation in most configurations. Additionally, Oracle’s policy requires you to license based on the maximum vCPU count of the instance type, and AWS features like “Optimize CPU” that allow you to disable vCPUs do not reduce your Oracle license requirement. You must license the full instance capacity.
Oracle permits license mobility between authorized cloud environments and on-premises. There is no penalty for moving licenses from AWS to OCI as part of a cloud migration. The licensing terms on the destination platform apply from the date of deployment.
The primary benefit applies to the Enterprise Edition under BYOL on OCI. Standard Edition 2 licensing in the cloud is more complex; SE2 is licensed per occupied socket, and the cloud-specific rules treat instance sizes differently. For any migration involving SE2, the licensing implications should be verified against the current Oracle policy document.
Oracle License Management Services is Oracle’s internal audit function. Audits can be triggered by licensing renewal negotiations, commercial discussions about transitioning from Oracle (including discussions about moving to a different database platform), large cloud migrations detected through Oracle’s partner networks, or routine audits of large Oracle customers. Cloud deployments are specifically flagged as an audit risk area. An organisation found to be under-licensed faces retroactive support fees at 22% per year for the unlicensed period, plus the cost of missing licenses at current list price
