HomeTraining AcademyOracle Licensing MasterySession 29
Oracle Licensing Mastery · Module 6 · Session 29 of 40 · 31:18

Oracle on AWS, Azure, and Google Cloud

Oracle runs in AWS, Azure, and Google Cloud under a published policy with sharp arithmetic: two vCPUs per processor license, no core factor, which roughly doubles the per core cost against on premises and quietly flatters OCI's BYOL ratios. This session reads the authorized cloud policy for what it is, a non contractual document your estate now relies on, runs the vCPU counting against real instances, walks the traps, autoscaling maxima, threading toggles, warm DR, and the ULA certification exclusion that has cost estates eight figures, and closes with the dedicated host exception that restores the core factor and the three homes comparison that keeps the estate choosing.

What you will be able to do after this session

  • 1Read the policy. Know what the authorized cloud environment policy is, covers, and, crucially, is not.
  • 2Count vCPUs correctly. License Oracle in AWS, Azure, and Google Cloud at the published ratios, without the core factor.
  • 3Price the premium. Understand why the same workload needs roughly twice the licenses in a hyperscaler as on premises.
  • 4Dodge the traps. Autoscaling, RAC, DR, and the ULA certification exclusion, found before they cost money.
  • 5Govern the estate. Keep hyperscaler Oracle inside the records, gates, and allocation discipline of session 25.

How the session works

A taught session with three knowledge checks: the 16 vCPU workload that doubles from 4 licenses on premises to 8 in AWS, the ULA certification exclusion that strips cloud deployments from the count, and the autoscaling group licensed for its average instead of its configured maximum. It closes with one workload counted four ways, on premises, EC2, dedicated host, and OCI BYOL, the comparison that decides the home.

Homework before the next session, about one hour

  • 1Inventory the hyperscaler Oracle. Every instance in AWS, Azure, or GCP: vCPUs, threading state, licenses allocated.
  • 2Audit the autoscaling. Every group running Oracle: configured maximum against licensed capacity. Close the gaps.
  • 3Check the ULA clause. If a ULA is live: what does certification say about cloud deployments? Read it now.
  • 4Run the three homes table. Your largest hyperscaler Oracle workload, counted all four ways. Does the current home win?
  • 5Feed the baseline. Cloud provider inventories wired into the deployment baseline, so the clouds join the position.
Learning the playbook and want it applied to your numbers? We work on contingency: 25% of what we save you. Nothing saved, nothing paid.
Review my deal