Oracle Database Licensing on AWS

Oracle Database runs on Amazon Web Services under three deployment paths. Bring your own license on EC2 virtual machines. License included on Amazon RDS for Oracle. Or third party hosting partners running on top of AWS infrastructure.

AWS sits inside the Oracle Authorized Cloud Environment list. The processor metric uses a two virtual CPU to one processor ratio when hyperthreading is enabled, and one to one when it is not. The Oracle core factor table does not travel into AWS compute.

Read this alongside the Oracle knowledge hub, the Oracle on Azure companion article, the Database 23ai guide, the ULA framework, and the Vendor Shield subscription.

Key Takeaways

What a database director and procurement lead need in 60 seconds

AWS is an Authorized Cloud Environment. Listed under the Oracle Cloud Licensing Policy alongside Azure and Google Cloud.
The metric is processor. Existing on premises processor licenses carry into AWS under bring your own license.
Two vCPU equal one processor with hyperthreading. Single threaded instance types map one to one.
The core factor table does not apply. No 0.5 multiplier on AWS EC2 compute.
Named User Plus minimum is twenty five per processor. Same floor as the on premises estate.
RDS for Oracle is license included or BYOL. The managed service ships in two metric modes.
Audit traps cluster around vCPU miscounting. Oversized instance types, replicas, and option spread are the top three findings.

Three deployment paths on AWS

Every Oracle Database workload on AWS sits in one of three buckets. Each bucket carries a distinct licensing posture, support model, and audit exposure.

Bring your own license on EC2

Customer managed virtual machine. EC2 compute, EBS storage, customer installed Oracle binaries.
Bring your own license. Existing processor or Named User Plus licenses cover the AWS footprint.
Customer Support Identifier carries. Active Oracle support required on the underlying licenses.
License metric scoped to vCPU. Authorized Cloud Environment rules apply, not the core factor table.

License included on Amazon RDS for Oracle

Managed database service. AWS operates the OS, patching, backups, and high availability layer.
License included edition. Standard Edition Two only. License rolled into the per instance hour rate.
Bring your own license edition. Standard Edition Two or Enterprise Edition on RDS, licensed on the AWS vCPU count.
No Oracle audit footprint under license included. The compliance question moves to AWS for the term of the instance.

Third party hosting on AWS

Hosting partner operates the workload. Often the same partner who runs the on premises Oracle estate.
Customer remains the licensee. Oracle contracts sit with the end customer, not the hosting partner.
Authorized Cloud Environment rules still apply. The hosting partner does not change the license metric.
Hosting agreement carries the audit obligation. Read the back to back terms before any audit notice arrives.

Authorized Cloud Environment rules on AWS

Oracle publishes the Cloud Licensing Policy on the Oracle Software Investment Guide. Three clauses drive the AWS posture and every buyer side renewal conversation.

The three governing clauses

vCPU mapping. Two virtual CPUs equal one Oracle processor when hyperthreading or multithreading is enabled.
Single threaded mapping. One virtual CPU equals one Oracle processor when hyperthreading is off.
Core factor exclusion. The 0.5 Intel and AMD multiplier that applies on premises does not apply on AWS EC2.

What the policy does and does not cover

In scope: Oracle Database, Middleware, and named Oracle Technology programs on EC2 or RDS BYOL.
Out of scope: Engineered Systems and most Oracle Applications. Licensing reverts to the underlying program terms.
Java SE Universal Subscription. Java cloud usage is governed by the Java metric, not the Authorized Cloud Environment.
Options and packs. Partitioning, RAC, Advanced Compression, and Diagnostics Pack all carry the same Authorized Cloud Environment vCPU rule when stacked on an Enterprise Edition base.

vCPU to processor math on AWS

The processor count drives the license total on every AWS Oracle deployment. The math is mechanical. Instance type, hyperthreading state, and Oracle option stacking all feed the calculation.

Worked vCPU example for a mid market Oracle estate on AWS

EC2 instance type	vCPUs	Hyperthreading	Oracle processors	EE plus options at list (USD)
r6i.4xlarge	16	On	8	720,000
r6i.8xlarge	32	On	16	1,440,000
r6i.16xlarge	64	On	32	2,880,000
x2idn.32xlarge	128	On	64	5,760,000
hpc7a.96xlarge	192	Off	192	17,280,000

Edge cases that catch most estates

Reserved Instance overlap. A one or three year Reserved Instance does not reduce the Oracle license footprint.
Spot fleet replicas. Short lived Spot instances still trigger a full Oracle processor obligation while running.
Cross region disaster recovery. The standby instance counts toward Oracle licensing, even if it is idle.
Auto Scaling groups. Peak concurrent instance count drives the license obligation, not the steady state.

RDS for Oracle mechanics

Amazon RDS for Oracle ships in two licensing modes. The choice determines who carries the Oracle audit obligation for the lifetime of the instance.

License included versus bring your own license

License included. Standard Edition Two only. Per instance hour rate covers compute, storage, and the Oracle license.
Bring your own license. SE2 or Enterprise Edition. Customer carries Oracle entitlement, AWS bills only the infrastructure.
Edition switch path. A move from SE2 to EE requires a BYOL license source and an RDS configuration change.
Multi AZ deployment. The standby replica counts under bring your own license. License included covers both nodes inside the per hour rate.

The hidden audit trap inside RDS BYOL

Under license included, the Oracle compliance question disappears for the duration of the subscription. Under bring your own license, every audit trap that lives on a customer managed EC2 instance also lives on RDS. Pick the model deliberately, not by default.

Audit traps and pitfalls on AWS Oracle estates

Oracle License Management Services targets AWS estates because the vCPU question is widely misread. Five traps catch the majority of audited tenants.

Five common AWS Oracle audit findings

Hyperthreading misread. Customer assumes single threading on instance types that ship with hyperthreading enabled by default.
Oversized instance type. Database migrated to a sixty four vCPU instance to clear a memory bottleneck, license footprint doubles.
Forgotten replica. Read replica or cross region standby running without a matching license source.
Options spread. Partitioning, Advanced Compression, or Diagnostics Pack enabled on the AMI without explicit licensing.
Named User Plus undercount. Twenty five per processor minimum missed on a small NUP licensed workload.

Buyer side defense moves

Inventory the AWS tenancy. Every Oracle binary, every region, every replica, every Auto Scaling group peak.
Run the options scan. DBA_FEATURE_USAGE_STATISTICS plus the Oracle options pack output, per instance.
Confirm hyperthreading state. EC2 documentation per instance family, plus the running instance metadata.
Reconcile the support contract. Customer Support Identifier active on every license deployed.
Pre price the gap. Calculate clean licensing before Oracle quotes a settlement.

Discount benchmarks on AWS footprints

Oracle treats AWS as competitive ground. Discount levels move with workload size, ULA leverage, and renewal posture.

Indicative buyer side discount ranges on AWS

Component	Discount range off list	Notes
Enterprise Edition base	60% to 75%	Driven by processor volume and ULA history
Database options	40% to 70%	Partitioning and Diagnostics Pack discount harder
RAC and Multitenant	30% to 65%	RAC discounting tightens on cloud only deployments
Support renewal uplift	0% to 8%	Default 8%, holdable at 0% with discipline

AWS is an Authorized Cloud Environment. The metric is processor. Two vCPU equal one license with hyperthreading on. The core factor does not travel. Every audit trap on an AWS Oracle estate starts inside this short list of rules.

What to do next

The seven step buyer side checklist below puts an Oracle on AWS estate on a clean licensing footing before the next Oracle conversation, audit, or renewal cycle.

Map every Oracle workload on AWS. EC2, RDS license included, RDS BYOL, hosted partner.
Confirm the deployment path. BYOL, license included, or hosting partner contract.
Catalog the instance types. vCPU count, hyperthreading state, region, replica posture.
Run the options usage scan. Every Oracle option flagged with a license source.
Reconcile the license entitlement. Active support, NUP floor, processor count, RDS BYOL allocations.
Pre price the gap. Use the vCPU table and the discount benchmarks above.
Open the Oracle conversation. On documented data, not on the auditor's spreadsheet.

Frequently asked questions

Is AWS an Authorized Cloud Environment for Oracle Database?

Yes. Amazon Web Services sits alongside Microsoft Azure and Google Cloud on the Oracle Cloud Licensing Policy. The policy governs the vCPU to processor mapping and applies to Database, Middleware, and a defined set of Oracle Technology programs. Engineered Systems and most Oracle Applications sit outside the policy.

How do I count Oracle processors on an AWS EC2 instance?

Take the vCPU count of the EC2 instance from the AWS console or the instance metadata service. Divide by two when hyperthreading is on, which is the default for almost every general purpose and memory optimized family. Use a one to one mapping when hyperthreading is off, common on the high performance HPC and HBv families. Round up to the nearest whole processor.

Does the Oracle core factor table apply on AWS?

No. Authorized Cloud Environment compute is licensed on the vCPU mapping, not the core factor. The 0.5 multiplier that applies to Intel Xeon and AMD EPYC on premises does not travel to AWS. The licensing math is mechanical and ignores the underlying chip family of the EC2 host.

What is the difference between RDS for Oracle license included and bring your own license?

License included covers Standard Edition Two only. The Oracle license is rolled into the per instance hour rate and the audit obligation moves to AWS for the duration of the subscription. Bring your own license covers SE2 or Enterprise Edition. The customer carries the Oracle entitlement, AWS bills only the underlying infrastructure, and the audit obligation stays with the customer.

Do Oracle options like Partitioning and Diagnostics Pack carry on AWS?

Yes. Every Oracle option stacks on an Enterprise Edition processor license, and the same Authorized Cloud Environment vCPU mapping applies. Track usage with the Oracle options pack output or the DBA_FEATURE_USAGE_STATISTICS view to confirm no option is in use without a matching license source.

How does Redress engage on Oracle on AWS?

Redress runs Oracle compliance review, AWS cost discipline, and renewal positioning inside the Vendor Shield subscription and the Renewal Program. Every engagement is led by a former Oracle commercial executive on the buyer side, with no Oracle or AWS sales conflict on the table.

How Redress engages on Oracle and AWS strategy

Redress runs Oracle and AWS advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment.

Read the related benchmarking page, the about us page, the locations page, and the contact page.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

Oracle Database on AWS. Licensed the buyer side way.