Oracle Cloud Licensing Policy — AWS, Azure, GCP, and the BYOL maths.

Authorized Cloud Environments — defined, then redefined.

Oracle's "Authorized Cloud Environment" (ACE) policy nominates Amazon EC2, Amazon RDS, Microsoft Azure and Google Cloud Platform as recognised public-cloud environments for Oracle Database, Middleware and Application licensing. Customers running Oracle products in those environments under BYOL terms apply the policy's counting rules. Customers running outside an ACE-recognised platform need to license against Oracle's standard processor metric without cloud-specific concessions.

For AWS and Azure, the policy specifies a 1:2 ratio — two vCPUs in the cloud equal one Oracle processor licence. For GCP, the same 1:2 ratio applies. For OCI, every two OCPUs counts as one processor (although OCPUs and vCPUs are not equivalent units, which is why OCI BYOL maths often surprises customers). The 1:2 factor was reduced from a more favourable earlier ratio in 2017 and has been the audit baseline since.

What 1:2 means in practice

A r5.4xlarge instance on AWS provides 16 vCPUs. Under ACE, that requires 8 Oracle Database EE processor licences. At list, that is approximately $380,000 plus 22% annual support. The same Oracle workload on OCI E4 Standard 4 shapes uses 4 OCPUs, requiring 2 Oracle Database EE licences. The asymmetry between OCI and non-OCI cloud is intentional and is the basis for Oracle's preference for OCI in any commercial conversation.

Where 1:2 does not apply.

The 1:2 ratio applies to Database Enterprise Edition and most other Oracle products on AWS and Azure under standard ACE terms. Several exceptions matter:

• Standard Edition 2 — counted by socket, not by vCPU. On cloud, SE2 is counted as one licence per four vCPUs.
• Hyper-threading — the 1:2 ratio applies when hyper-threading is enabled. With hyper-threading disabled (less common on cloud), one vCPU equals one processor.
• Named User Plus minimums — NUP minimums on cloud follow the same counting rules but apply against the cloud-counted processor count, not against the underlying hardware.
• Options and Packs — counted at the same rate as the underlying database. Partitioning on a 16-vCPU EC2 instance is 8 Partitioning processor licences.
• Application licences — Oracle E-Business Suite and other application licences on cloud follow distinct counting rules (often based on named users) that do not follow the 1:2 ratio.

Why dedicated shapes often make sense.

A common point of confusion is that the ACE policy counts vCPUs on the underlying instance — not on the workload running inside the VM. A workload that uses 4 cores out of a 16-vCPU EC2 instance is still licensed against 8 Oracle processors. The fence that resolves this is to size cloud instances precisely against the licensed Oracle workload. Customers running Oracle BYOL on oversized shapes routinely have licence positions 2-3x larger than they would on right-sized shapes.

For Azure, Dedicated Hosts can provide additional fencing — but Azure Dedicated Hosts are not automatically recognised as more favourable than shared infrastructure under ACE. The relevant fence is shape sizing, not host type. AWS Dedicated Hosts can sometimes attract favourable treatment but the policy is silent on this; relying on it requires contractual language, not a policy assumption.

RDS for Oracle

Amazon RDS for Oracle is the most common Oracle deployment pattern on AWS. RDS supports BYOL and licence-included options. BYOL is favoured when the customer has under-utilised perpetual licences; licence-included is favoured for tactical or short-term deployments. The licence-included pricing includes Database Enterprise Edition only — Partitioning, ASO, Advanced Compression and other options must still be separately licensed even under licence-included, unless using RDS Oracle's specific "Enterprise Edition" offering with restrictions.

OCI Universal Credits and the strategic discount.

Oracle's commercial strategy on cloud has been to use OCI Universal Credits as the financial vehicle for BYOL-to-cloud migration. A customer with significant on-prem Oracle commitments can typically convert a portion of those commitments to OCI Universal Credits at terms more favourable than equivalent AWS or Azure BYOL. The relevant levers in those negotiations:

• Support credit — a portion of existing support payments converted to OCI credits, reducing net new spend.
• Discount on annual commit — significant discounts on OCI list prices for multi-year commitments.
• Free egress — limited free egress allowances that compare favourably with AWS and Azure.
• Service-specific discounts — Autonomous Database and Exadata Cloud Service often have discount levels exceeding general OCI discounts.

The trade-off is operational. OCI is improving rapidly but lacks the breadth and ecosystem of AWS, Azure or GCP. Customers running Oracle as a strategic platform often find OCI compelling. Customers running Oracle as a legacy workload to be exited rarely do.