OCI or AWS. Two conversion rules, one workload.

The same database server needs a different number of Oracle licenses depending on which cloud it lands in. Not because the hardware changes, but because Oracle publishes two entirely separate conversion regimes, and only one of them preserves the arithmetic you use on premises.

Which clouds does the Authorized Cloud Environment policy actually cover?

Three of them: Amazon Web Services, Microsoft Azure and Google Cloud. Oracle's own cloud is deliberately outside that policy, which is the single most misunderstood fact in this comparison.

Oracle sets out the counting rules in its cloud licensing policy and names the qualifying providers in the authorized cloud environments list. Oracle Cloud Infrastructure is governed instead by the service descriptions attached to your cloud order.

The three rules inside the policy that move money

• The vCPU conversion. With hyperthreading enabled, two vCPUs count as one Processor license. Without it, one vCPU counts as one.
• No core factor. The policy states that the processor core factor table does not apply in an authorized cloud environment. Every core counts in full.
• An edition ceiling. Standard Edition 2 may only be licensed on instances up to 8 vCPUs, so the edition cannot follow a growing workload up the instance families.

None of those three rules apply on Oracle's own cloud. That is not a loophole, it is the design: Oracle prices its own platform to make the license you already own go further there.

Named User Plus does not disappear in the cloud

User based licensing still carries minimums, and the policy restates them in cloud terms rather than importing the on premises figure unchanged. Read the current policy text for the minimum that applies to your edition before you assume the number you use in the data center.

Where the OCI ratio comes from

From Oracle's cloud service descriptions, not from the partitioning policy and not from the authorized cloud policy. The mapping to know is one Processor license per two OCPUs, and an OCPU is a physical core presenting two vCPUs on x86 shapes.

Confirm the exact ratio for the specific service in your order. Oracle publishes the conversion per service, and it differs between compute, the database services and the Exadata services.

How many licenses does the same server need on each platform?

Twice as many on AWS as on OCI, for identical physical hardware. That is the arithmetic that decides most of these comparisons, and it is worth walking through slowly because almost every business case gets it wrong in the same direction.

The worked example

• The requirement. A production Oracle Database Enterprise Edition workload that needs 16 physical x86 cores.
• In your data center. 16 cores at the 0.5 core factor is 8 Processor licenses.
• On AWS. Those 16 cores present 32 vCPUs. Divided by two, that is 16 Processor licenses, with no core factor to soften it.
• On OCI. Those 16 cores are 16 OCPUs. At one Processor license per two OCPUs, that is 8 Processor licenses.
• The gap. 8 Processor licenses, which is 380,000 dollars at the published Enterprise Edition list price, plus 22 percent of that every year in support.

Why turning hyperthreading off does not help

Because the policy moves the ratio when you move the threads. Disable simultaneous multithreading on a 16 core instance and you present 16 vCPUs instead of 32, but the conversion becomes one vCPU per Processor license, so you still need 16.

The number that matters is physical cores. Any advice that tells you to change the thread setting to cut Oracle licenses on an authorized cloud is arithmetic that does not survive a second reading.

The instance families where the trap actually bites

• Instance types without simultaneous multithreading. One vCPU is one core, so a 16 vCPU instance is 16 Processor licenses rather than 8.
• Burstable and shared tenancy families. Fine technically, awkward to evidence, and rarely appropriate for a licensed database anyway.
• Autoscaling groups. The license count follows the maximum the group can reach, not the average it usually runs at.
• Non production copies. Development and test instances are licensable unless a specific term says otherwise, and they are where cloud sprawl shows up first.

What does OCI give back that the authorized clouds do not?

Three things: a conversion that preserves your on premises arithmetic, a managed database tier you can run owned licenses against, and the option to use Real Application Clusters at all.

Bring your own license into a managed service

On OCI you can apply owned perpetual licenses to the managed database services and pay the lower infrastructure rate, as described on Oracle's bring your own license page. The equivalent on AWS is a self managed database on EC2, or Amazon RDS under its own rules.

Whether that is actually cheaper for you is a separate question with its own arithmetic. We work it through in the bring your own license versus license included comparison.

What you give up in exchange

• Commercial concentration. Database, infrastructure and support all sit with one vendor at the same renewal, which is the opposite of leverage.
• Consumption commitments. Oracle's credit model is prepaid and unused credit is generally forfeited, so the commitment size becomes its own negotiation.
• Application tier economics. The license advantage applies to Oracle software. It does not follow your application servers, object storage or data pipeline.
• Regional coverage. Check the region list for the specific service, not the region list for the cloud.

White Paper · Oracle

Oracle on Azure & AWS BYOL

Count the Oracle cloud licence before you commit. Read it free.

Read the white paper

What can you run on one platform and not the other?

Clustering is the hard boundary. Real Application Clusters is not available on the authorized clouds, and no amount of license budget changes that, so an architecture that depends on it narrows the platform list before any cost model opens.

The capability differences that actually decide architectures

The Amazon RDS edition trap

Amazon RDS for Oracle offers a license included model, and it covers Standard Edition 2. Enterprise Edition on Amazon RDS for Oracle requires you to bring your own licenses, which removes the pattern most teams assume exists when they plan to retire owned licenses by moving to a managed service.

That single line has redirected several migration plans we have reviewed. Check it before the business case is signed, not after.

Multicloud changed the question in the last two years

Oracle now operates its own database hardware inside the other clouds. Oracle Database at Azure came first, with Google Cloud and AWS equivalents following, and they place Oracle managed Exadata in a hyperscaler region.

• The counting rules follow the service, not the cloud. These are Oracle services, so the service description governs, not the authorized cloud vCPU conversion.
• Clustering comes back. Because the hardware is Exadata, the capability gap largely closes for the workloads that fit.
• The contract is with Oracle. Which affects who audits you and where the commercial leverage sits.
• Region coverage is uneven. Availability is expanding, so confirm the current list for your regions rather than a slide from last year.

We cover the commercial shape of these arrangements in the Oracle multicloud licensing guide.

Where is each platform actually cheaper?

OCI is usually cheaper for the Oracle database estate and AWS is usually cheaper for everything around it. Any comparison that produces a single winner for a mixed estate has probably answered the wrong question.

The three lines most models leave out

• Support on the owned licenses. If you keep perpetual licenses alive to use them in a cloud, the annual support line follows them there.
• The migration itself. Data movement, testing and parallel running is routinely the third largest line in a five year model and the first one omitted.
• The commitment you sign to get the rate. Both vendors price against a spend commitment, and an unmet commitment is a cost, not a saving.

How to keep both vendors honest

Run the comparison in license units first and currency second. Once the license count is settled you are negotiating rates against a fixed denominator, which is the only position where competing quotes actually compare.

Which seven questions decide the platform?

Answer these in order. Most estates find that the first three settle the question before anyone opens a pricing tool.

1. Do you own perpetual Enterprise Edition licenses with support active? If yes, the conversion difference is real money and OCI starts ahead.
2. Does the architecture need clustering? If yes, the authorized clouds are out for that workload.
3. Is the database staying on Oracle for five years? If not, optimise for exit speed rather than license efficiency.
4. What is the edition? Standard Edition 2 runs into the 8 vCPU ceiling on authorized clouds and needs a growth plan.
5. Where does the rest of the estate already run? Data gravity and an existing spend commitment are real costs, not preferences.
6. What does the commitment cost if you miss it? Model the downside of both commitments, not just the discounted rate.
7. Who audits you afterwards? Concentrating database, infrastructure and support with one vendor changes your position at every future renewal.

Where the common advice on OCI versus AWS is wrong

The standard advice is to pick the cloud with the better infrastructure rate and treat licensing as a detail to sort out later. We disagree, and the engagement record is blunt about it. In about six of ten platform comparisons we built in 2024 and 2025 the license count was the largest line in the five year model, and it is fixed by policy before a single rate is negotiated. Worse, the direction of the error is consistent: teams carry the on premises core factor into an authorized cloud model, understate the AWS position by close to half on database compute, and only discover it after the commitment is signed. Settle the license count first. Then negotiate rates.

The rate card is negotiable. The conversion ratio is not. Settle the license count first, because it is the only number in the model neither vendor will move for you.

What should a buyer do next?

Do this before you accept either vendor's model as the baseline. It takes a week and it changes the shape of the negotiation.

1. Pull the perpetual license inventory, confirm which lines have active support, and note the options and packs attached to each.
2. Convert the target workload to physical cores, then apply each platform's rule separately and write both license counts down.
3. Check the edition on every workload against the 8 vCPU ceiling and the managed service edition limits.
4. Confirm which workloads genuinely need clustering, and separate them from the ones that need availability by another route.
5. Price migration and parallel running explicitly, then add the support line on any license you are keeping alive for cloud use.
6. Model the downside of both spend commitments, not only the discounted rate each vendor is quoting.
7. Read the Oracle cloud licensing policy guide and the Oracle on AWS licensing guide, then take independent buyer side advice before signing either contract.

Frequently asked questions

Is Oracle Cloud Infrastructure an Authorized Cloud Environment?

No. Oracle's authorized cloud policy covers Amazon Web Services, Microsoft Azure and Google Cloud. Oracle's own cloud sits outside it and is governed by the service descriptions attached to your cloud order, which carry different conversion ratios.

What is the license ratio on AWS for Oracle Database?

Two vCPUs count as one Processor license when hyperthreading is enabled, and one vCPU counts as one Processor license when it is not. The processor core factor table does not apply, so a 32 vCPU instance needs 16 Processor licenses.

What is the license ratio on OCI?

One Processor license covers two OCPUs. Because an OCPU is a physical core presenting two vCPUs on x86 shapes, the same silicon that needs 16 Processor licenses on an authorized cloud needs 8 on OCI. Confirm the ratio for the specific service in your order.

Does the core factor apply in the cloud?

Not on an authorized cloud. Oracle's policy states that the processor core factor table is not applicable there, which is why cloud license counts come out roughly double the equivalent on premises count for x86 hardware.

Does turning off hyperthreading reduce Oracle licenses on AWS?

No. Turning it off halves the vCPU count but also changes the conversion to one vCPU per Processor license, so the count lands in the same place. The number that matters is physical cores.

Can you run Real Application Clusters on AWS?

Not on a plain authorized cloud environment. The routes to clustering are Oracle Cloud Infrastructure, Exadata Cloud at Customer, an Oracle operated multicloud service inside a hyperscaler region, or your own data center.

How is Standard Edition 2 treated on authorized clouds?

It may only be licensed on instances of up to 8 vCPUs. That ceiling matters because it caps the growth path for a Standard Edition estate on AWS, Azure or Google Cloud without an edition change.

Which platform is cheaper for Oracle workloads?

OCI usually wins on the Oracle database estate because the conversion halves the license count, and AWS usually wins on the application tier and surrounding services. Most large estates end up running both and using that position at each renewal.