Oracle counts AWS vCPUs under the Authorized Cloud Environment policy. The rule is a policy, not a contract. Buyers that ignore the gap between policy and contract overpay the audit by two to four million dollars.
Oracle Database and Middleware licensing on AWS follows the Authorized Cloud Environment policy. The policy maps Oracle processor licenses to AWS vCPUs at a ratio of two vCPUs per license. The mapping is a published policy, not a clause in the Oracle Master Agreement.
The gap between policy and contract drives audit risk. Buyers that read the policy as the authority overpay. Buyers that read the contract first hold a defensible floor at audit.
Oracle defines an Authorized Cloud Environment as AWS, Azure, and a small set of named cloud regions. The processor license metric maps to vCPUs inside these environments. The map is two vCPUs per processor license on hyperthreaded families.
One Oracle processor license covers two AWS vCPUs on instance families that enable hyperthreading. On instance types that do not enable hyperthreading the mapping is one vCPU per license. The buyer side reads the family list before the order document.
Standard Edition Two is capped at sixteen AWS vCPUs across the entire AWS account. The cap is not per instance. A multi account estate carries one cap per account.
Oracle publishes the cloud environment list and updates it from time to time. AWS commercial regions are listed. AWS GovCloud and the China regions are not. Running in an unlisted region carries the audit assumption that no policy applies.
The Oracle Master Agreement defines the processor metric without naming AWS. The cloud policy lives on the Oracle website as a separate document. The audit defense reads both layers and the gap between them.
The Oracle Master Agreement names the processor metric. The metric counts physical cores multiplied by a core factor. The agreement does not contemplate vCPUs.
The Authorized Cloud Environment policy maps the processor metric to vCPUs at the two vCPU ratio. The policy is published. The policy carries the words "for licensing purposes" but does not amend the agreement.
The Oracle auditor relies on the policy as the count rule. The buyer side that signs an audit settlement under the policy may concede a position the contract does not require. Independent advisory reviews both layers before any settlement.
| Layer | Source | Binding | Buyer side position |
|---|---|---|---|
| Master Agreement | Signed contract | Yes | Processor metric, no vCPU language |
| ACE Policy | Oracle website | Guidance | vCPU count, not in contract |
| Order Document | Signed order | Yes | Quantity, term, support |
| Audit Letter | Vendor notice | Optional | Forty five day response window |
Oracle does not offer a formal license mobility program for AWS. The customer brings the existing license to the cloud under BYOL terms. The mobility rules are inferred from the policy, not stated in the contract.
BYOL is the practical entry path. The customer owns a perpetual Oracle license and the matching support. The license is deployed on EC2 under the cloud policy.
AWS RDS for Oracle supports both BYOL and License Included modes. License Included carries the Standard Edition Two ceiling. Enterprise Edition workloads run BYOL only.
Oracle limits license reassignment to once every ninety days. The rule applies to BYOL on AWS. Frequent rotation of instances or accounts can trigger the rule.
Oracle Enterprise Edition, Standard Edition Two, and the database options carry different cloud rules. The buyer side reads the matrix before each deployment.
Enterprise Edition runs on EC2 or on AWS RDS BYOL. The vCPU mapping applies. Options like Partitioning, Diagnostics, and Tuning carry separate licenses and separate audit risk.
Standard Edition Two carries the sixteen vCPU cap per AWS account. The license includes a small set of features and excludes the database options. The edition suits small to mid sized workloads.
Oracle does not certify Real Application Clusters on AWS. Running RAC on AWS carries a support risk. Active Data Guard is supported. Single Instance Failover via clustering is a workaround.
The Oracle LMS audit script reads EC2 metadata, the Oracle inventory file, and the database feature usage tables. The output is the audit position. The buyer side that has not run a pre audit script carries a surprise.
The LMS script reads the instance type, the region, and the vCPU count from the EC2 metadata service. The script also reads instance tags where available.
The script reads the Oracle inventory file on each EC2 instance. The file lists installed Oracle products. The auditor reads installed as deployed.
Oracle Database tracks feature usage in the DBA_FEATURE_USAGE_STATISTICS view. The script reads the table. A single accidental feature touch can flag the option as in use.
The Oracle on AWS renewal motion repeats every twelve to thirty six months. The buyer side that runs the pre renewal review resets the floor.
The window opens one hundred eighty days before the support anniversary. The buyer side that starts earlier holds a wider option set. The window closes ninety days before the anniversary on most contracts.
The buyer side that wants out of Oracle on AWS has four exit options. Migrate to AWS RDS License Included. Migrate to AWS RDS for PostgreSQL or Aurora. Move to OCI under a separate cloud agreement.
Third party support for Oracle on AWS is available from a small set of providers. The route cuts support cost by forty to seventy percent. The route forfeits the right to new versions and patches.
The checklist takes the buyer from the AWS audit notice to the executed strategy. The earlier the work starts, the wider the option set.
Oracle counts processor licenses on AWS under the Authorized Cloud Environment policy. The rule maps two AWS vCPUs to one Oracle processor license on hyperthreaded instance families. On non hyperthreaded families the ratio is one vCPU per license. The policy is published on the Oracle website and does not amend the Master Agreement.
The Authorized Cloud Environment policy is published guidance from Oracle. It is not a clause in the Oracle Master Agreement. The auditor relies on the policy as the count rule. Independent advisory reads both the contract and the policy before any audit settlement and identifies the gap between them.
Oracle does not certify Real Application Clusters on AWS. The buyer side that deploys RAC on EC2 carries a support and certification risk. Active Data Guard is supported on AWS under BYOL. Single Instance Failover via clustering is a workaround pattern many enterprises use in place of RAC.
Oracle Standard Edition Two is capped at sixteen AWS vCPUs across the entire AWS account. The cap is per AWS account, not per instance. A multi account estate carries one cap per account. The edition excludes the database options and suits small to mid sized workloads on AWS.
AWS RDS for Oracle supports both BYOL and License Included modes. BYOL on RDS follows the ACE policy and the two vCPU rule. License Included is limited to Standard Edition Two. Enterprise Edition on RDS is BYOL only and requires the customer to provide the matching support entitlement.
Common audit triggers include a renewal letter that is met with a price push back, a perceived ULA exit move, and a sudden increase in AWS spend that becomes visible to Oracle account teams. Feature usage statistics that show options flagged as in use without matching license entitlement are a separate trigger.
Across twenty two Oracle on AWS reviews completed by Redress the median audit gap before settlement was four million dollars. The gap traced primarily to accidental option usage and to BYOL deployments that exceeded the licensed processor count. Independent review before the audit letter closes most of the gap.
Redress runs the pre audit script, the AWS estate scan, the feature usage review, and the renewal motion inside the Vendor Shield subscription and the Renewal Program. The work includes the order document review, the cloud policy comparison, the option hygiene plan, and the contract negotiation against the prior renewal floor.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Oracle service line, and the Software Spend Assessment.
Read the cloud licensing guide, the Azure article, the Oracle Knowledge Hub, the benchmarking service, and the Benchmark Program.
The companion playbook covers the 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 a policy that lives outside the contract. The buyer side that reads the contract first and the policy second carries the audit defense the customer that reads the policy first does not.
We have run twenty two Oracle on AWS reviews with median four million dollar audit gap closed. 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.
