Oracle Database Bring Your Own License on AWS runs under the Oracle Cloud Computing Environments Policy. The policy is non contractual. The buyer side team that follows the document and pins the architecture captures the saving and holds the audit position.
Oracle Database BYOL on AWS runs under the Oracle Cloud Computing Environments Policy. The policy maps two vCPUs to one Oracle license on standard EC2 instance families with hyperthreading enabled. The rule is non contractual and Oracle reserves the right to change it.
The buyer side team that pins the architecture, documents the deployment, and locks the policy version captures the saving cleanly. The four AWS deployment options each carry a different math. RDS for Oracle is the most common trap because the AWS vCPU count and the Oracle vCPU count diverge.
Oracle publishes the Oracle Cloud Computing Environments Policy on the Oracle website. The policy maps Oracle license counts to authorised cloud environments. AWS is an authorised environment. The policy is a one page document that Oracle can change unilaterally.
AWS, Microsoft Azure, and Google Cloud Platform are authorised environments. Oracle Cloud Infrastructure is the preferred environment. Other clouds require separate Oracle approval.
Two vCPUs map to one Oracle Processor license on instance families with hyperthreading. One vCPU maps to one Oracle Processor license on instance families without hyperthreading.
Oracle has revised the policy three times in five years. Each revision tightened the mapping. The customer that pins the deployment to a specific policy version through contract language reduces the change risk.
The policy is not part of the Oracle Master Agreement. Oracle can change the policy without contractual notice. The mitigation is the contractual reference to the policy version at signing.
The vCPU to license math depends on the EC2 instance family and the hyperthreading state. AWS reports vCPU as a logical core. Oracle counts vCPU under the policy. The two counts match when hyperthreading is enabled.
M, C, R, and X families typically run with hyperthreading enabled. Two vCPUs map to one Oracle Processor license. A 16 vCPU instance requires 8 Oracle Processor licenses.
T family burstable instances and some HPC families run without hyperthreading. One vCPU maps to one Oracle Processor license. The customer who switches to a non hyperthreaded family doubles the license cost.
Named User Plus licenses are permitted on AWS under the policy. The minimum count of 25 users per Processor license applies. The metric is the user count, not the vCPU count.
Real Application Clusters, Partitioning, Active Data Guard, and other options each carry their own license. The Processor license on each option matches the Database Processor count.
| EC2 instance | vCPU count | Hyperthreading | Oracle Processor licenses |
|---|---|---|---|
| m5.4xlarge | 16 vCPU | Yes | 8 licenses |
| m5.8xlarge | 32 vCPU | Yes | 16 licenses |
| r5.4xlarge | 16 vCPU | Yes | 8 licenses |
| c5.9xlarge | 36 vCPU | Yes | 18 licenses |
| t3.2xlarge | 8 vCPU | No | 8 licenses |
| x1e.16xlarge | 64 vCPU | Yes | 32 licenses |
AWS offers four ways to run Oracle Database. Each option has a different license math, a different operational profile, and a different audit posture. The buyer side team picks the option that fits the workload and the license inventory.
The customer runs Oracle Database directly on EC2 instances under the cloud policy. Two vCPUs to one Processor license on hyperthreaded families. The customer manages the database and the OS. The audit defense is the EC2 instance type record.
AWS Dedicated Hosts give the customer a physical server. Oracle counts physical cores, not vCPUs. The math reverts to the Oracle Master Agreement metric definitions. The option works for very large workloads.
AWS managed Oracle Database service. RDS bills the AWS infrastructure. The customer brings the Oracle license. The vCPU count diverges between AWS billing and Oracle policy.
Oracle Database on AWS hardware in the customer data center. The Oracle metric depends on the Outposts instance family. The license inventory must cover the full Outposts vCPU footprint.
Amazon RDS for Oracle is the most popular path and the most common audit finding. AWS RDS bills the customer for the RDS instance class. Oracle counts the underlying vCPU. The two counts diverge when the RDS instance class abstracts the physical layer.
The customer brings the Oracle Processor license to RDS. AWS bills RDS infrastructure separately. The license covers the database engine and the chosen options.
Multi AZ RDS deployments run a standby replica on a separate instance. Oracle requires Active Data Guard license to cover the standby if the standby is open for read. The customer who enables read on the standby triggers the Active Data Guard requirement.
AWS RDS offers a license included path for Standard Edition Two. The customer pays AWS for the license. The path is not BYOL and is not under the cloud policy. The path is the simplest audit position.
Enterprise Edition is BYOL only on RDS. AWS does not offer license included for Enterprise Edition. The customer must bring the Processor license and document the vCPU count.
Oracle Master Agreement allows the customer to deploy licensed software on any authorised infrastructure. The cloud policy authorises AWS. The customer can move the license between on premise and AWS at will, subject to the metric mapping rule.
The Oracle license travels with the workload. The customer is not charged a mobility fee. The deployment record at any point in time defines the license consumption at that point.
Temporary workload bursts to AWS for testing, development, or seasonal peak are permitted. The customer documents the burst and returns the license to the home environment at the end of the burst.
Disaster recovery deployments on AWS are permitted. Active Data Guard, GoldenGate, or other replication options require their own license. The DR deployment is licensed in the same way as the primary.
Oracle Database for development and test does not require Processor licenses if no production data runs and no production access is granted. The Named User Plus minimum applies to all developers.
Oracle audits the AWS deployments through the License Management Services soft audit motion. The defense pattern relies on documented evidence per deployment. The customer that produces the evidence cleanly walks the audit. The customer who cannot produce the evidence pays the Oracle finding.
Every EC2 instance, every RDS instance, every Dedicated Host with the vCPU count, the instance family, the hyperthreading state, and the deployment date.
Every Oracle Processor license, every Named User Plus license, every option license with the order document reference and the maintenance status.
Each deployment mapped to a specific license. No deployment without a license. No license double counted across deployments.
The Oracle Cloud Computing Environments Policy version at the deployment date archived in the deployment record.
The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.
Yes, under the Oracle Master Agreement and the Oracle Cloud Computing Environments Policy. AWS is named as an authorised cloud environment. The customer brings the existing Processor or Named User Plus licenses and deploys on AWS subject to the metric mapping rule. The license is not modified by the deployment.
Oracle audits AWS deployments through the License Management Services soft audit motion or a formal contractual audit. The auditor requests the EC2 instance inventory, the vCPU count per instance, the hyperthreading state, and the license inventory. The defense is the deployment record archived against the policy version at the deployment date.
Two vCPUs map to one Oracle Processor license on instance families with hyperthreading enabled. One vCPU maps to one Oracle Processor license on instance families without hyperthreading. The mapping sits in the Oracle Cloud Computing Environments Policy. The mapping does not apply to Dedicated Host where physical cores are counted directly.
Enterprise Edition on RDS is BYOL only. Standard Edition Two is available as license included where AWS bills the license through the RDS hour rate. The buyer side team chooses based on the workload, the existing license inventory, and the audit posture preference. License included is the simpler audit position. BYOL is the lower cost when licenses are already owned.
Multi AZ RDS deployments run a standby replica that is not open for read by default. The default Multi AZ deployment does not trigger Active Data Guard. The customer who enables read on the standby triggers the Active Data Guard requirement and must license the standby with Active Data Guard.
Yes. The Oracle Cloud Computing Environments Policy is a non contractual document Oracle can revise at any time. Three revisions have happened in the last five years. The mitigation is the contractual reference in the order document that pins the policy version applicable to the customer to a specific date or version number.
Redress runs the deployment review, the license inventory audit, the policy version analysis, and the audit defense inside the Vendor Shield subscription and the Oracle service line. The work covers the AWS architecture review, the Oracle license mapping, and the negotiation of the policy version reference in the order document.
Dedicated Host gives the customer a physical server and reverts the metric to the Oracle Master Agreement core count. The audit posture is strongest. Dedicated Host typically prices at 2 to 3 times the equivalent EC2 instance. Most customers run a hybrid pattern with Dedicated Host for production and EC2 for non production workloads.
Redress runs this practice inside the Vendor Shield subscription, the Oracle service line, the Oracle Knowledge Hub, and the Software Spend Assessment.
Read the related Oracle Database on AWS overview, the Oracle Database licensing guide, the Oracle cloud environments guide, and the AWS advisory practice.
The companion playbook covers the Oracle Unlimited License Agreement decision tree, certification mechanics, and the negotiation moves that protect the customer at exit.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →Oracle on AWS is not difficult. The difficulty is the document Oracle wrote, can change, and is not in your order. The defense is the deployment record that pins the policy version to the workload.
We have reviewed 90 AWS BYOL deployments with zero audit findings against documented architectures. Every engagement starts with one conversation.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
