The Oracle Hyperscalers Licensing Guide
Running Oracle on AWS, Azure, or Google Cloud is governed by Oracle's authorised cloud environment policy, which counts two vCPUs as one processor licence where hyperthreading is on, and by the BYOL rules that decide whether owned entitlement covers the deployment. The policy is contractual, not a statute, and that is the point: what it counts, and how, is negotiable territory. This guide explains the rules and how to deploy on a hyperscaler without overpaying.
Executive summary
Most large Oracle estates now run at least partly on a hyperscaler, AWS, Microsoft Azure, or Google Cloud, rather than only on Oracle's own cloud. Oracle permits this through its authorised cloud environment policy, a document that names the eligible providers and sets the counting rule: on an authorised hyperscaler, two virtual CPUs generally equal one Oracle processor licence where hyperthreading is enabled, and one vCPU equals one licence where it is not. That single rule, and the BYOL eligibility behind it, determines whether a hyperscaler deployment is economical or quietly more expensive than the on premises estate it replaced.
The critical thing to understand is that the authorised cloud policy is a contractual position Oracle publishes, not a law. It can and does change, it differs in important details from the on premises core factor rules, and it interacts with the newer database@cloud and Oracle managed offerings that place Oracle hardware inside hyperscaler regions. A customer that treats the policy as immovable, applies on premises counting habits to the cloud, or assumes BYOL coverage without confirming eligibility, ends up overcounting vCPUs, paying twice on support, or sitting on an undefendable compliance position in someone else's data centre.
This white paper explains the authorised cloud environment rules across the three major hyperscalers, the vCPU counting mathematics, the BYOL and database@cloud options, and the audit exposure unique to running Oracle on infrastructure Oracle does not control. It then sets out a buyer side framework for deploying on a hyperscaler at the lowest defensible cost. Read it alongside our cloud and OCI licensing service and the BYOL licensing guide.
What is inside
- The authorised cloud environment policy and the eligible hyperscalers.
- The vCPU counting rule and how it differs from the on premises core factor.
- BYOL eligibility on AWS, Azure, and Google Cloud, and the double payment trap.
- Database@cloud and Oracle managed options inside hyperscaler regions.
- A buyer side framework for deploying on a hyperscaler at the lowest defensible cost.
About the practice
Oracle Software Licensing is an independent buyer side advisory practice with offices in New York, London, and Stockholm. Across more than 750 Oracle engagements the practice has delivered an average audit reduction of seventy percent and over $300M in client savings, drawing on 20+ years of combined licensing experience. We do not resell or implement Oracle software. We structure hyperscaler deployments, count vCPUs, and defend audits on behalf of the buyer. Explore our OCI licensing guide or request a consultation.