Most Oracle Unlimited License Agreements predate the AWS migration that followed. The counting rules for AWS are written into Oracle policy, not the contract, and the gap creates real exposure at certification. This article is the 2026 buyer side reference on ULA usage of AWS infrastructure.
Oracle Unlimited License Agreements predate the cloud era for most enterprises. The counting rules for AWS sit inside the Oracle Authorized Cloud Environments policy, not the ULA contract itself. AWS counts at a two virtual CPU per Oracle processor ratio on hyper threaded instances.
The certification math depends on instance shape, region, and BYOL versus license included posture. Most ULA holders run material exposure on AWS without knowing it. This article fixes that.
Pair this article with the Oracle knowledge hub, the Oracle advisory practice, the ULA decision framework, the renewal checklist, and the 90 day ULA certification checklist before any AWS migration of Oracle workloads.
An Oracle ULA grants unlimited deployment of named products for the contract term, on terms set in the order document. The cloud question is whether AWS deployments count toward the certified perimeter at exit, and whether the deployed footprint translates to permanent licenses after exit.
Most ULA contracts predate the policy and grant unlimited deployment within an enterprise definition. The cloud question is settled by the policy version in force at certification, not the contract. The buyer side discipline is to read both documents side by side before any AWS expansion.
Oracle has on rare occasion attempted to limit cloud deployment under a ULA. The buyer side legal position is that the policy in force at the contract effective date controls. Document the policy version at signing.
The processor counting math on AWS depends on the instance type and the hyper threading state. The default math under the Authorized Cloud Environments policy is two virtual CPUs per Oracle processor. Single thread instance shapes count at one vCPU per processor.
| Instance family | vCPU per Oracle processor | Notes |
|---|---|---|
| m5, m6i, c5, c6i, r5, r6i | 2 vCPU per processor | Hyper threaded by default |
| m6g, c6g, r6g (Graviton) | 1 vCPU per processor | Single thread Arm cores |
| x2idn, x2iedn, u-12tb1 | 2 vCPU per processor | High memory, hyper threaded |
| i4i, i3en (storage) | 2 vCPU per processor | Hyper threaded by default |
Amazon RDS for Oracle is the managed database service. RDS accepts Bring Your Own License under the standard authorized cloud math, or sells license included as a per hour SKU. The choice is a contract design decision, not an operational one.
RDS for Oracle BYOL counts the deployed database compute against the ULA at certification. License included on RDS does not draw from the ULA. The choice between the two is often made by the cloud team without visibility into the ULA exit math.
A pre certification inventory of every RDS Oracle instance and its license model is the buyer side starting point.
ULA certification is the snapshot event that converts unlimited deployment into permanent licenses. The AWS footprint at the snapshot date counts toward the certified processor count, on the authorized cloud math.
| Scenario | On premise | AWS BYOL | Total processors | Risk |
|---|---|---|---|---|
| Steady state | 200 processors | 40 processors | 240 processors | Low. Inventory is current. |
| Mid migration | 120 processors | 180 processors | 300 processors | High. Snapshot timing matters. |
| Peak then trim | 200 processors | 160 processors | 360 processors | High. Trim before snapshot. |
The snapshot date is set by the contract end date. The buyer side discipline is to plan the AWS footprint to its highest legitimate level on the snapshot date, then trim after certification. Oracle license counts after certification cannot be reduced through snapshot trimming.
The certification submission carries the deployed processor count, the deployed instance list, and the policy version reference. Document everything. The audit window after certification is open.
The five moves below recur across every Oracle ULA on AWS engagement Redress runs. None of them require Oracle approval. All of them require the buyer side evidence pack.
The AWS Oracle inventory found seventy two RDS BYOL instances on hyper threaded shapes. Recounted at certification, the footprint converted to ninety six permanent processors, locking the buyer in to a stronger post ULA position.
The seven step checklist below is the buyer side starting position for any Oracle ULA on AWS engagement.
Yes. The Oracle Authorized Cloud Environments policy lists AWS, Azure, and OCI Classic as approved environments for Database, Middleware, and selected applications. The policy controls the counting math at certification. Read the version of the policy in force at the ULA effective date and pin that version in the certification submission.
The AWS processor count at the snapshot date converts to permanent licenses, on the authorized cloud math. Two virtual CPUs count as one Oracle processor for hyper threaded instance shapes. Single thread shapes count at one vCPU per processor. The submission carries the instance list and the deployed processor equivalent.
Trimming after certification does not reduce the certified license count. The snapshot date is what matters. The buyer side discipline is to stage the AWS deployment to its highest legitimate level on snapshot day, then trim after the certification submission lands.
License included on RDS does not draw from the ULA at certification. The Oracle license is bundled into the AWS per hour rate. BYOL on RDS counts toward the ULA, on the same processor math as EC2. The buyer side decision is whether the per hour bundle is cheaper than the ULA derived BYOL position.
OCI is treated under the Oracle on Oracle rule, with a more favorable processor math. OCI cores count one to one against Oracle licenses, with no two vCPU rule. The OCI position is a separate evaluation from the AWS position and should be modeled independently.
Redress runs the AWS Oracle inventory, the hyper threading audit, the policy version pin, the certification model, and the snapshot timing plan. Engagements run as a focused six week sprint or as part of the wider ULA exit program. Always buyer side, never Oracle paid.
Redress runs ULA on AWS reviews as part of the Oracle advisory practice. The work covers the cloud inventory, the policy pin, the hyper threading audit, the certification model, and the snapshot timing plan. Programs run as a focused engagement or as part of the wider Vendor Shield subscription.
Read the related Renewal Program, Benchmark Program, Software Spend Assessment, Benchmarking framework, about us, management team, locations, and contact pages.
A buyer side reference on the ULA entry decision, the certified perimeter, the quarterly health check, the exit project model, and the post exit license set. Includes the executive scorecard template used across hundreds of Oracle engagements.
Independent. Buyer side. Built for CFOs, CIOs, and vendor management teams carrying Oracle relationships. No Oracle influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The AWS Oracle inventory found seventy two RDS BYOL instances on hyper threaded shapes. Recounted at certification, the footprint converted to ninety six permanent processors, locking the buyer in to a stronger post ULA position.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
ULA on AWS counting lessons, RDS BYOL findings, certification snapshot patterns, hyper threading audit wins, and the wider Oracle commercial leverage signals across every program we run.
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.
