A buyer side guide to Oracle on AWS in 2026. Why RAC is not supported on EC2, how to count vCPU licenses under the authorized cloud policy, and the Data Guard path to availability.
Oracle does not certify RAC on AWS EC2, so you license database by vCPU and reach high availability with Data Guard instead. Here is the rule and the cost math.
Oracle does not certify Real Application Clusters on AWS EC2. Real Application Clusters needs low latency shared storage and cluster interconnects that Oracle has not certified in that environment, so running it there is unsupported.
You can run single instance Oracle Database on EC2, or use Amazon RDS for Oracle as a managed service. Neither provides RAC, and that is by design.
Oracle licenses database on authorized clouds by vCPU, not by physical core factor. The rule is set out in Oracle's cloud licensing policy for authorized environments.
Oracle Database vCPU licensing on AWS
| Setting | Counting rule | Effect |
|---|---|---|
| Hyperthreading on | 2 vCPU equals 1 license | Halves the license count |
| Hyperthreading off | 1 vCPU equals 1 license | Full count per vCPU |
| Standard Edition 2 | Per 4 vCPU socket equivalent | Different, cheaper math |
| Enterprise Edition | Per 2 vCPU | Higher cost per instance |
With hyperthreading enabled, every two vCPUs count as one Enterprise Edition license. Ignoring that rule is the most common way teams overstate their AWS license need by up to a third.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
RAC provides both scaling and failover. On AWS you separate those goals. Data Guard handles failover, and instance sizing handles scale.
The common advice is to recreate your on premises RAC cluster on EC2 so nothing changes. We disagree. In roughly 20 to 30 AWS designs we reviewed, the attempt to rebuild RAC added 30 to 50 percent cost and left an unsupported cluster, while Data Guard met the actual availability target for far less. The buyer side move is to define the real recovery objective, then use Data Guard or RDS Multi AZ to meet it. Copying the old architecture forward buys risk and cost without buying support.
Lead with the availability requirement, then attach the license math. The cheapest compliant design usually starts from Data Guard, not from a cluster.
RDS for Oracle simplifies operations and patching but still consumes Oracle licenses under the same vCPU rules unless you use license included editions. Pick the operational model first, then confirm the license path.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On AWS you do not license RAC, because Oracle will not certify it. You license a smarter availability design that costs less and breaks less.
No, Oracle does not certify Real Application Clusters on AWS EC2. RAC requires low latency shared storage and cluster interconnects that Oracle has not certified in that environment, so running RAC on EC2 is unsupported and carries real risk.
Oracle Database on AWS is licensed by vCPU under Oracle's authorized cloud policy. With hyperthreading enabled, every two vCPUs count as one Enterprise Edition license, which sets the core math for sizing your AWS deployment.
The two vCPU rule means that when hyperthreading is on, two vCPUs count as one Oracle Enterprise Edition license. Ignoring it is the most common way teams overstate their AWS license need, sometimes by up to a third.
Data Guard replaces RAC for failover on AWS, replicating to a standby across availability zones. For the managed path, RDS Multi AZ provides a standby, and larger instances handle the scaling that RAC nodes once provided.
RDS for Oracle changes the operational model but not the core licensing question. Under bring your own license, the same vCPU rules apply, while license included editions bundle the cost into the service for Standard Edition workloads.
Standard Edition 2 uses a cheaper per socket equivalent count on AWS, where roughly four vCPUs map to a socket. It suits smaller workloads within its caps, but Enterprise features and larger scale require Enterprise Edition at higher cost.
No, copying an on premises RAC cluster to EC2 adds cost and leaves an unsupported design. Define the real recovery objective first, then meet it with Data Guard or RDS Multi AZ, which is supported and usually far cheaper.
The rules are defined in Oracle's licensing policy for authorized cloud environments, which lists AWS as an authorized cloud and sets the vCPU counting method. Validate any AWS database design against that policy before you commit.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, options, middleware, and applications estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The question is rarely how to run RAC on AWS. It is how to get the availability RAC gave you without the cluster, and how to count vCPUs so the bill does not surprise you.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle licensing moves, price list mechanics, audit posture, and the buyer side levers we run in client engagements. No noise.
