Oracle RAC on AWS. The cluster you cannot run.

Oracle Real Application Clusters is not certified or supported on Amazon EC2, so you cannot run native RAC on AWS the way you would on premises. What you can do is license Oracle Database on EC2 using Oracle's authorized cloud counting rules, and reach high availability through Data Guard or a managed service rather than RAC.

This guide is for Oracle and cloud teams planning a database move to AWS in 2026. Read it with the Oracle Database licensing on AWS guide and the Oracle licensing on AWS overview.

Can you run Oracle RAC on AWS?

Not in the supported sense. RAC needs shared storage and an interconnect that Oracle certifies, and that certification does not extend to EC2. So the practical question is how to license a single instance or a Data Guard pair instead.

Why is RAC not supported on EC2?

RAC depends on a certified cluster configuration. AWS EC2 is an authorized cloud for Oracle Database, but Oracle has not certified the RAC clusterware stack on it, so running it is unsupported.

What are the high availability alternatives?

You reach availability through replication and failover rather than a shared cluster. Each option has a different license effect.

• Data Guard: a standby instance, licensed the same as the primary.
• Managed service: a third party or partner managed Oracle on AWS.
• Multi AZ design: built on Data Guard, not on RAC.

Does a Data Guard standby need a license?

Yes, in almost all cases. An open or actively applying standby is licensed like the primary. A truly cold standby has narrow rules, so confirm the configuration against your contract.

How do you count Oracle licenses on AWS EC2?

AWS uses Oracle's authorized cloud counting rule, which is based on vCPUs, not the on premises core factor table. Oracle publishes the policy in its cloud licensing document.

How does bring your own license work here?

You apply existing Oracle Database licenses to the EC2 instance and count vCPUs under the cloud policy. Oracle documents the authorized environments in its cloud licensing policy.

Does edition change the math?

Yes. Standard Edition 2 has socket and vCPU caps that differ from Enterprise Edition. Pick the edition before you size the instance, because the cap can decide the instance family.

What is the most common licensing mistake?

Sizing the instance for performance first, then discovering the vCPU count drives more licenses than budgeted. Size the license and the instance together, not in that order.

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.

What to do next

1. Drop RAC from the AWS design and plan availability around Data Guard.
2. Confirm whether the instance runs hyper threading on or off.
3. Count vCPUs under the authorized cloud rule, not the on premises core factor.
4. Decide between Enterprise Edition and Standard Edition 2 before sizing.
5. License any Data Guard standby to match the primary unless a narrow exception applies.
6. Right size the instance so the vCPU count matches your entitlements.
7. Document the configuration so it stands up in an Oracle review.

Frequently asked questions

Can you run Oracle RAC on AWS EC2?

No, not in a supported way. Oracle does not certify Real Application Clusters on AWS EC2, so native RAC is not a supported configuration there. Teams reach high availability through Data Guard or a managed service instead.

How do you license Oracle Database on AWS?

You count vCPUs under Oracle's authorized cloud policy. With hyper threading on, two vCPUs equal one processor license. With it off, one vCPU equals one license. This replaces the on premises core factor table.

Does a Data Guard standby on AWS need a license?

In almost all cases yes. An open or actively applying standby is licensed like the primary. Only a narrow cold standby exception exists, so confirm the configuration against your Oracle contract before relying on it.

Is AWS an authorized cloud for Oracle?

Yes. AWS is listed as an authorized cloud environment in Oracle's cloud licensing policy, which is why the vCPU counting rule applies. The soft partitioning rules still govern how you size the instance.

Does Standard Edition 2 change the AWS license math?

Yes. Standard Edition 2 carries socket and vCPU caps that differ from Enterprise Edition. Choose the edition before sizing the instance, because the cap can decide which instance family you can use.

What is the cheapest compliant way to run Oracle on AWS?

Right size the instance to the smallest vCPU count that meets performance, choose the edition deliberately, and use Data Guard only where availability requires it. Match entitlements to vCPUs so you neither over buy nor fall short.