Oracle Licensing on AWS: BYOL, vCPU Counting & the Core Factor Trap — 2026 Guide

An Authorized Cloud Environment (ACE) is a public cloud Oracle has named in its cloud policy — currently Amazon EC2, Amazon RDS, and Microsoft Azure — where Oracle permits per-vCPU licence counting instead of licensing the entire physical host. This matters because AWS never exposes the physical server to you, so without the ACE policy Oracle's default position would be to licence every core in the underlying hardware.

The critical caveat: the ACE policy is a policy document, not a contractual term. It is not referenced in your Oracle Master Agreement and Oracle reserves the right to revise it. Buyers who rely on the policy alone carry the risk that Oracle changes the counting rules mid-deployment. The defensible position is to negotiate your cloud deployment rights directly into the Oracle ordering document. See our Oracle cloud licensing guide for how this fits the wider OCI, Azure and BYOL picture.

An AWS vCPU is a single hardware thread, not a full core. Most EC2 instance types ship with hyper-threading on, so two vCPUs map to one physical core. Oracle's ACE policy then sets Enterprise Edition at 2 vCPUs per Processor licence. The table below shows the counting rules across the environments enterprises most often compare.

Worked example: an m5.8xlarge EC2 instance exposes 32 vCPUs with hyper-threading on. Oracle Database EE on that instance needs 32 ÷ 2 = 16 Processor licences. Named User Plus minimums still apply — 25 NUP per Processor — so a NUP licence would require at least 400 NUP. Right-sizing the instance is the fastest lever; see Oracle license optimization.

The Core Factor Table is Oracle's on-premises chart that discounts certain processors — Intel and AMD x86 cores are multiplied by 0.5. It is the single biggest source of mis-counting we see on AWS, because finance teams assume the on-prem maths carries over. It does not. Under the ACE policy, AWS counting is purely vCPU-based: 2 vCPUs = 1 licence for EE, full stop.

The compliance consequence is severe and asymmetric. An enterprise that applies the 0.5 Core Factor to a 32-vCPU instance buys 8 Processor licences when Oracle's policy requires 16 — a 100% shortfall that surfaces in an Oracle audit as a back-licence claim plus back-support. Across 600+ engagements, roughly 7 in 10 enterprises running Oracle on AWS carry this exact error (Oracle Licensing Experts benchmark, 2026).

BYOL is the model where you reuse existing perpetual Oracle licences in the cloud rather than renting Oracle's. The steps to do it defensibly:

1. Establish your true entitlement — the exact Processor and NUP quantities on your Oracle ordering documents.
2. Size the AWS deployment in vCPUs and convert to Processor licences using the ACE rule (2 vCPU = 1 for EE).
3. Confirm you hold enough licences for the cloud footprint plus any on-premises use that continues — licences are not duplicated for free.
4. Verify each database option and pack (Partitioning, Diagnostics, Tuning, RAC) is separately licensed for the AWS cores.
5. Record the cloud deployment in your licence ledger so it holds up under Oracle's own audit methodology.

Done wrong, BYOL creates a dual-use exposure: counting the same licences against on-prem and AWS at once. This is a frequent audit finding. Our Oracle cloud advisory team builds the entitlement-to-deployment map before Oracle does.

License Included (LI) bundles the Oracle Database licence into Amazon's per-hour price and is available only for Standard Edition 2 — no separate Oracle purchase, no audit exposure on the database licence itself. BYOL lets you run Enterprise Edition or SE2 on RDS using licences you own, counted under the same ACE vCPU rules as EC2.

The economics flip on utilisation and edition. For steady-state Enterprise Edition workloads where you already own perpetual licences, BYOL is almost always cheaper than re-renting through Oracle. For bursty or short-lived SE2 workloads, License Included avoids a capital purchase. We model both against your Oracle database licensing position before you commit.

The four findings Oracle's LMS team most often raises on AWS estates:

1. Core Factor misuse — counting at 0.5 instead of 2 vCPU = 1 licence. Typically a 100% shortfall.
2. Dual-use BYOL — the same perpetual licences claimed against on-prem and AWS simultaneously.
3. Unlicensed options — Partitioning, Diagnostics Pack, Tuning Pack and RAC enabled on AWS cores without matching entitlement.
4. Policy reliance — no contractual cloud rights, leaving the deployment exposed if Oracle revises the ACE policy.

If an audit letter has already arrived, do not run Oracle's scripts before you control the data — see our Oracle audit guide and audit defense service.

The fastest cost lever is instance right-sizing: every 2 vCPUs you remove from an EE instance removes a full Processor licence and its 22% annual support. Disabling hyper-threading where workloads allow halves the vCPU count but changes the conversion to 1:1, so model both. Compare BYOL against License Included for each workload, and benchmark any new Oracle cloud commitment before signing — our Oracle contract negotiation and compliance review teams do this buyer-side. For the sibling clouds, see Oracle licensing on Azure and Oracle licensing on GCP.