Short answer: Oracle BYOL on AWS EC2 and RDS both use Oracle's Authorized Cloud Environment rule — 2 vCPUs per Processor license with hyperthreading on — not the on-premise Core Factor Table. A 16-vCPU instance needs 8 Oracle Processor licenses on either platform. The license count is identical; what differs is control, supported options, and audit exposure.
Key Takeaways
- On both EC2 and RDS, Oracle counts 2 vCPUs per Processor license when hyperthreading is enabled — and 1 vCPU per license when it is not (Oracle Authorized Cloud Environments policy).
- Oracle's Core Factor Table does not apply on AWS. The familiar 0.5 multiplier for x86 cores is gone, which makes a cloud core roughly twice as expensive to license as the same on-premise core.
- A 16-vCPU deployment requires 8 Oracle Processor licenses on EC2 and on RDS — the counting math is the same; the platform choice is operational, not a license discount.
- BYOL on both platforms requires active Oracle support on the licenses; third-party support customers cannot use those licenses for AWS BYOL.
- Across 600+ engagements, AWS BYOL deployments are over-licensed or mis-sized in roughly 1 in 3 cases reviewed (Oracle Licensing Experts benchmark, 2026) — usually from counting full instance vCPUs instead of right-sizing the shape.
How Does Oracle Count Licenses for BYOL on AWS?
Oracle BYOL (Bring Your Own License) is Oracle's program that lets enterprises apply existing perpetual Processor or Named User Plus licenses to software running on a public cloud, paying the cloud provider only for infrastructure. On AWS, the counting rule comes from Oracle's Licensing Oracle Software in the Cloud Computing Environment policy — the document that defines AWS and Microsoft Azure as Authorized Cloud Environments. Under that policy Oracle counts virtual CPUs (vCPUs), not physical cores, and it does not apply the Core Factor Table.
The rule is specific: with hyperthreading enabled, 2 vCPUs equal one Oracle Processor license; with hyperthreading disabled, 1 vCPU equals one license. Because AWS enables hyperthreading on almost every instance family by default, the working number for most deployments is 2 vCPUs per license. This is the single most important sentence on this page, and it applies identically to EC2 and to RDS. The platform you choose does not change the divisor — it changes everything around it.
Oracle's cloud policy is a policy document, not a contractual term — it is not part of your Master Agreement, and Oracle can revise it. That cuts both ways. It gives you a workable counting method today, but Oracle reserves the right to change the vCPU ratio. Capture the version of the policy in force when you deploy, and keep evidence-based records of your instance configurations. When Oracle's audit team challenges a cloud deployment, the policy version and your configuration logs are the evidence that protects you.
Oracle BYOL on AWS EC2: Full Control, Full Responsibility
Amazon EC2 (Elastic Compute Cloud) gives you a raw virtual machine on which you install and manage Oracle Database yourself. Under BYOL, you license the vCPUs assigned to the instance using the 2-vCPU rule. An r5.4xlarge with 16 vCPUs needs 8 Oracle Processor licenses; an r5.8xlarge with 32 vCPUs needs 16. Because you control the operating system and the database, EC2 is the only AWS path that supports the full range of Oracle Database options — Real Application Clusters (RAC) is not supported on standard EC2 the way it is on-premise, but Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack, In-Memory and GoldenGate all run normally when separately licensed.
The audit exposure on EC2 is the options layer. Oracle Database EE on EC2 ships with management packs that are trivially easy to enable — Diagnostics Pack and Tuning Pack are accidentally active in more than 40% of enterprise environments. On a self-managed EC2 instance, nothing stops a DBA from switching on a pack that you have not licensed, and Oracle's LMS scripts will find it. Right-sizing EC2 BYOL means licensing the vCPUs you actually run and locking down which options are enabled.
Oracle BYOL on AWS RDS: Managed, but Constrained
Amazon RDS (Relational Database Service) for Oracle is a managed service: AWS handles provisioning, patching, and backups, and you consume Oracle Database by instance class. RDS supports two licensing models — BYOL, where you bring your own EE or SE2 licenses, and License Included, where AWS bundles SE2 licensing into the hourly rate. Enterprise Edition on RDS is available under BYOL only; there is no License Included path for EE.
The counting rule on RDS is identical to EC2: a db.r5.4xlarge with 16 vCPUs requires 8 Oracle Processor licenses under BYOL. What changes is the option set. RDS for Oracle supports a defined subset of Oracle features and options; some EE options are available, others are not, and the managed layer restricts the patching and configuration freedom you get on EC2. For a database estate that does not need exotic options, RDS removes operational overhead. For a workload that depends on tight control of Oracle internals, RDS can force compromises EC2 would not.
Sizing an AWS BYOL migration?
Our Oracle Cloud advisory service verifies BYOL entitlements, models the vCPU counts for every shape, and right-sizes EC2 versus RDS before you deploy — not after Oracle's audit team finds the gap.
EC2 vs RDS: The Counting Rules Side by Side
The table below sets the two models against each other on the dimensions that actually decide cost and compliance. Note that the per-license divisor is the same — the differences live in control, supported options, and where the audit risk concentrates.
| Dimension | AWS EC2 (BYOL) | AWS RDS for Oracle (BYOL) |
|---|---|---|
| Counting unit | vCPU | vCPU |
| License ratio (HT on) | 2 vCPUs = 1 Processor license | 2 vCPUs = 1 Processor license |
| Core Factor Table | Not applied | Not applied |
| Licenses for 16 vCPUs | 8 Processor | 8 Processor |
| Edition support | EE, SE2 (BYOL) | EE (BYOL only), SE2 (BYOL or License Included) |
| Oracle options | Full range, separately licensed | Defined subset only |
| Patching / admin | You manage everything | AWS-managed |
| Primary audit exposure | Accidentally enabled options/packs | Entitlement vs vCPU count mismatch |
| Active Oracle support required? | Yes | Yes |
Why Is the Core Factor Table Missing on AWS?
On-premise, Oracle's Core Factor Table assigns a 0.5 multiplier to standard x86 processors, so 16 physical cores require 8 Processor licenses. Enterprises instinctively expect the same benefit in the cloud — and Oracle is happy to let them assume it. The cloud policy quietly removes the Core Factor and replaces it with the flat 2-vCPU rule. Since a vCPU is a hyperthread (half a physical core), 2 vCPUs map to one physical core, and one physical core now needs a full license rather than half of one. The net effect: a cloud core is licensed at roughly twice the on-premise rate. Buyers who model AWS BYOL on their on-premise core-factor math under-count by 2x and walk straight into a back-license claim.
A financial-services firm migrated a 32-core on-premise Oracle EE estate to EC2 and budgeted 16 Processor licenses using their old 0.5 Core Factor. The correct AWS count for 64 vCPUs was 32 licenses. We caught the 16-license gap during pre-migration review, right-sized the shapes down to the workload's real demand, and rebuilt the entitlement position before deployment. See our client case studies for comparable cloud-migration outcomes.
How Do You Right-Size Oracle BYOL on AWS?
Right-sizing is where buyers reclaim the money Oracle's defaults quietly take. The process is the same discipline we apply on every cloud engagement, in order:
- Measure real utilization first. Size the instance to the workload's actual CPU demand, not the on-premise server it replaced. Oversized shapes are the single largest source of wasted BYOL licenses.
- Count vCPUs at the 2:1 ratio for every shape, and confirm hyperthreading status. A handful of instance families let you disable hyperthreading, shifting to a 1:1 count that can be worse, not better — model both.
- Reconcile against entitlement. Compare the vCPU-derived license requirement to the Processor licenses you actually own on active support. Any shortfall is audit exposure; any surplus is shelfware you can redeploy.
- Lock down options. On EC2, disable management packs and options you have not licensed. On RDS, confirm the option group only enables licensed features.
- Document the policy version. Record the Oracle cloud policy in force at deployment and keep configuration evidence for audit defense.
Our Oracle license optimization service runs this reconciliation as a forensic exercise, and our Oracle compliance review closes any gap before Oracle's audit monitoring identifies it. For the full cloud framework, see our Oracle Cloud Licensing Guide and the related Oracle BYOL to OCI guide.
Frequently Asked Questions
Does Oracle BYOL on AWS EC2 count vCPUs or physical cores?
On EC2, Oracle counts vCPUs under its Authorized Cloud Environment rule, not the underlying physical cores directly. With hyperthreading enabled, 2 vCPUs equal one Oracle Processor license. A 16-vCPU EC2 instance therefore needs 8 Processor licenses. The on-premise Core Factor Table does not apply.
How does Oracle count licenses on AWS RDS for Oracle?
RDS uses the same rule as EC2: 2 vCPUs per Processor license with hyperthreading on. Because RDS abstracts the host, you license the instance class's vCPU count directly. A db.r5.4xlarge with 16 vCPUs requires 8 Oracle Processor licenses under BYOL.
Is the Oracle Core Factor Table used on AWS?
No. Oracle's Core Factor Table is replaced on Authorized Cloud Environments by the flat vCPU rule: 2 vCPUs equal one Processor license with hyperthreading on, or 1 vCPU per license without it. This makes a cloud core roughly twice as expensive to license as the same on-premise core.
Can I use Oracle BYOL on AWS RDS?
Yes. RDS for Oracle supports BYOL for both EE and SE2, and License Included for SE2. Enterprise Edition is BYOL only — there is no License Included path. BYOL on RDS requires the licenses to be on active Oracle support.
Which is cheaper for Oracle licenses, EC2 or RDS?
Neither — the license count is identical for the same vCPU total. The decision is operational: EC2 gives full control and the complete option set but you manage everything; RDS cuts admin overhead but supports only a subset of options. Choose on workload needs and supported features, not on a license discount that does not exist.
Do third-party support customers qualify for AWS BYOL?
No. Oracle BYOL requires the underlying licenses to be on active Oracle support. Licenses moved to a third-party support provider to save the 22% annual fee cannot simultaneously be used for BYOL on AWS. Enterprises must choose between the two strategies and model the five-year total cost of each.