OCI vs AWS. Oracle workload licensing compared.

The Authorized Cloud Environment policy

Oracle Policy 070617 defines the Authorized Cloud Environment. AWS, Azure, and Google Cloud are the three named clouds. Oracle Database and middleware run on those clouds under specific BYOL rules.

The ratio table

What the table does not cover

• Standard Edition 2: the socket based metric does not translate cleanly to vCPU. Oracle SE2 deployments on AWS run at a different ratio.
• NUP minimums: Named User Plus minimums still apply on the perpetual base. AWS deployment does not waive them.
• Options and packs: Diagnostics, Tuning, Partitioning all carry separate metrics. Each runs against the same vCPU base.

OCI BYOL to PaaS economics

The OCI database service converts BYOL perpetual licenses into a deeper subscription discount. AWS does not offer the same conversion. This is the largest single economic difference between the two clouds for Oracle workloads.

The BYOL to PaaS conversion

• Database service on OCI: the customer brings perpetual database licenses and receives the BYOL rate.
• Autonomous Database on OCI: BYOL applies and converts at the same processor ratio.
• Exadata Cloud on OCI: BYOL applies plus the Exadata software fee is absorbed into the OCPU rate.
• Universal Credits commit: the commit unlocks an additional 25 to 50 percent discount on the BYOL rate.

AWS RDS for Oracle

AWS RDS for Oracle accepts BYOL but does not absorb the Oracle support cost into the subscription. The customer still pays the 22 percent Oracle support line on the perpetual base. The AWS RDS rate is on top of that.

RAC and high availability options

Oracle Real Application Clusters is not supported on AWS Authorized Cloud Environment. The same applies to Azure and Google Cloud. RAC requires Oracle Database at Customer or OCI dedicated region deployment.

What runs where

• RAC: OCI dedicated region or Oracle Database at Customer only.
• Data Guard: all four clouds.
• GoldenGate: all four clouds. Replication target matters more than the source.
• Active Data Guard: all four clouds. License entitlement must be confirmed.

TCO comparison across five years

The numbers are illustrative. The variance band shifts by workload mix, region choice, and the Universal Credits commit tier. Build the model with measured baseline data.

Seven decision points on OCI vs AWS

1. BYOL or subscribe. BYOL is cheaper if support is active. Subscription is cheaper if the perpetual base is unused.
2. RAC requirement. If RAC is required, OCI or Database at Customer are the only routes.
3. Universal Credits commit. The OCI commit unlocks the deepest Oracle discount band.
4. Existing AWS EDP. If the customer has an AWS EDP, the Oracle workload spend on AWS can count toward the EDP commit.
5. Hyperthreading posture. Disabling hyperthreading on AWS doubles the BYOL cost. Confirm the AWS instance type.
6. Multi cloud leverage. Running both clouds creates negotiating leverage against Oracle on every renewal.
7. Migration cost. The cost of moving the workload is the third largest line in the TCO model. Do not skip it.

What to do next

1. Pull the Oracle perpetual license inventory and confirm active support.
2. Model the BYOL ratio against AWS EC2 with hyperthreading enabled.
3. Model the BYOL to PaaS conversion against OCI database service rates.
4. Confirm RAC requirements with database architecture.
5. Benchmark Universal Credits discount against the AWS EDP discount band.
6. Build the five year TCO model on both clouds with migration cost included.
7. Engage independent buyer side advisory before signing either cloud contract.

Frequently asked questions