Running Oracle on AWS, Azure, or Google Cloud changes the licensing math. The Authorized Cloud Environment rules set the vCPU conversion, and the traps are counting, support, and the OCI interconnect.
Running Oracle on AWS, Azure, or Google Cloud follows the Authorized Cloud Environment policy, not the on premises core factor. This guide covers the vCPU conversion, BYOL rules, the traps, and the buyer side moves.
Oracle treats AWS, Azure, and Google Cloud as Authorized Cloud Environments. A separate policy, not the on premises core factor table, sets how licenses convert there.
The rules are published in the Oracle licensing in authorized cloud environments policy. It defines the vCPU based counting that replaces the physical core factor.
BYOL is the primary way to run Oracle economically on a third party cloud. You carry an owned license and pay only the cloud infrastructure.
BYOL requires the owned license on active support, mapped to a single home. The alternative is a License Included option from the cloud marketplace, which bundles the license at a higher rate. Oracle also runs a low latency interconnect with Microsoft Azure and with Google Cloud. Oracle also offers BYOL to OCI with its own conversion.
Oracle licensing across cloud providers
| Environment | Counting basis | Licensing options |
|---|---|---|
| AWS | vCPU | BYOL or License Included |
| Azure | vCPU | BYOL, plus OCI interconnect |
| Google Cloud | vCPU | BYOL, plus OCI interconnect |
| OCI | OCPU | BYOL or License Included |
Three traps recur, and each shows up after the workload has moved. A baseline before migration avoids all three.
The most common trap is misjudging the vCPU count on the target shape. The second is leaving the owned license pinned to an on premises server while also using it in the cloud.
The common advice is that moving Oracle to AWS, Azure, or Google Cloud lowers licensing cost because you escape Oracle infrastructure. We disagree. In the moves we have advised, the licensing requirement on the target cloud often rose, because vCPU counting and the loss of the on premises core factor increased the processor count rather than reducing it. The buyer side move is to model the vCPU based requirement before the migration, confirm BYOL eligibility, and compare it honestly against OCI, where Oracle prices its own software most aggressively. Escaping Oracle hardware does not mean escaping Oracle licensing.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Leaving Oracle hardware is not leaving Oracle licensing. Model the vCPU requirement on the target cloud before you move, not after the invoice lands.
White Paper · Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Three moves protect the budget. Each happens before the workload migrates.
Model the vCPU requirement on the target shape, confirm BYOL eligibility, and separate each owned license into a single home before the move.
Oracle treats them as Authorized Cloud Environments under a separate policy. Licenses convert based on vCPUs allocated, not the on premises physical core factor, which changes the processor count on the target cloud.
No. The on premises Processor Core Factor Table does not apply in Authorized Cloud Environments. Counting is based on vCPUs under the Oracle cloud licensing policy instead.
Bring Your Own License lets you carry an owned Oracle license onto AWS, Azure, or Google Cloud and pay only the cloud infrastructure. The license must be on active support and mapped to a single home to stay eligible.
Not always. The vCPU counting and loss of the core factor can raise the license requirement even as hardware cost falls. Model the requirement and benchmark against OCI before assuming a saving.
Oracle offers a low latency interconnect between OCI and Azure or Google Cloud, letting the database run on OCI while the application runs on the other cloud. It changes where workloads can sit for licensing purposes.
Misjudging the vCPU count on the target shape, losing BYOL eligibility through lapsed support, and counting the same license on premises and in the cloud. All three appear after the move unless you baseline first.
No. A BYOL license must have a single home. Using the same entitlement on an owned server and a cloud instance at once is double counting and fails an audit.
Benchmark both. Oracle prices its own software most aggressively on OCI, including BYOL, so a fair comparison against the vCPU requirement on AWS, Azure, or Google Cloud should be part of every decision.
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 leaders running the next renewal cycle.
Engage independent buyer side Oracle licensing experts. We do not resell. We do not implement. We sit on your side of the table.
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →Oracle on someone else cloud is still Oracle licensing. The Authorized Cloud Environment policy, not the cloud provider, decides what you owe. Read the policy before you lift and shift.
