OCI vs AWS for Oracle workloads — the Hyderabad / Mumbai region reality check, 2026
Published 26 May 2026
· By
Pawan Sharma
· Cloud / Oracle
· 20 min read
For the first time, India has four public-cloud regions that can credibly host Oracle Database workloads: OCI Mumbai (BOM, 2019), OCI Hyderabad (HYD, 2020), AWS Mumbai (ap-south-1, 2016) and AWS Hyderabad (ap-south-2, 2022). That's good news — and it makes the "where do we land this Oracle stack?" question harder, not easier. This is the documentation-backed reality check: where Oracle DB actually runs on each cloud, what each platform supports, what BYOL math really looks like, and the five mistakes Indian buyers keep making on this decision.
1. India regions, at a glance
Both clouds now operate paired India regions — designed to enable in-country DR without crossing the border. The two are not equivalent in age, AZ topology, or service catalogue depth.
| Region | GA | Topology | Notes |
|---|---|---|---|
| AWS Mumbai (ap-south-1) | 2016 | 3 AZs | Oldest India region. Broadest AWS service catalogue. Default for India workloads on AWS. |
| AWS Hyderabad (ap-south-2) | Nov 2022 | 3 AZs | Newer. Service catalogue is narrower than ap-south-1 — verify each managed service is in-region before designing on it. |
| OCI Mumbai (BOM) | 2019 | Single Availability Domain (multi-FD) | OCI's single-AD regions still offer Fault Domains for HA within the AD. Multi-AD HA needs cross-region DR. |
| OCI Hyderabad (HYD) | 2020 | Single AD (multi-FD) | Designed as the BOM DR pair. Inter-region DR for Exadata + Autonomous is standard architecture here. |
2. Where Oracle DB actually runs on each cloud
"Run Oracle on AWS" and "run Oracle on OCI" are not symmetric statements — the platforms expose Oracle Database through very different products.
AWS — 3 ways to run Oracle
- RDS for Oracle — fully managed.
License Includedis SE2 only; for Enterprise Edition you must BYOL. No OS access; no RAC; no Exadata. - RDS Custom for Oracle — managed with OS-level access. BYOL only. EE supported. The escape hatch when you need DBA-level control of the database host but still want some RDS automation.
- EC2 BYOL — self-managed Oracle on EC2. Full control, full operational ownership. No managed-service overhead, no managed-service automation either.
Not on AWS, period: Real Application Clusters (RAC), Exadata, Exadata Cloud@Customer.
OCI — 4 ways to run Oracle
- Base Database Service (DBCS) — Oracle DB on VM or bare-metal in OCI. SE2 or EE. License Included or BYOL. RAC option available.
- Exadata Database Service — Exadata in the cloud. Smart Scan, storage cells, the full Exadata feature set. X8M / X9M / X10M shapes.
- Autonomous Database — fully self-driving. ATP (Transaction Processing), ADW (Data Warehouse), and JSON DB variants. Shared or Dedicated infrastructure.
- Exadata Cloud@Customer — Exadata hardware racked in your data centre; OCI control plane. The route when data must stay on-prem but you want the Exadata + OCI experience.
OCI-only territory: RAC, Exadata, Cloud@Customer, Autonomous DB.
3. Feature support matrix
This is where the platforms genuinely diverge — and where most buyer surprises hide.
| Capability | AWS RDS Oracle | AWS RDS Custom | AWS EC2 BYOL | OCI Base DB | OCI Exadata |
|---|---|---|---|---|---|
| Real Application Clusters (RAC) | No | No | No | Yes (RAC option) | Yes |
| Exadata features (Smart Scan, storage cells) | No | No | No | No | Yes |
| Automatic Storage Management (ASM) | Managed away | OS-level | Yes | Yes | Yes |
| Data Guard (standby) | Multi-AZ only (mirror, not Data Guard) | Yes (manual) | Yes | Yes | Yes |
| Active Data Guard (read-on-standby) | No | Manual | Yes (licensed) | Yes (option) | Yes |
| Multitenant (CDB/PDB) | Yes | Yes | Yes | Yes (default) | Yes |
| Partitioning (option) | Yes | Yes | Yes | Yes | Yes |
| Transparent Data Encryption (TDE) | Yes | Yes | Yes | Yes | Yes |
| Database Vault | No | Yes | Yes | Yes | Yes |
| EE licence on managed service | BYOL only | BYOL only | BYOL only | LI or BYOL | LI or BYOL |
4. The pricing reality (per-OCPU / per-vCPU)
Three pricing knobs decide most landed cost on either cloud: licence posture (License Included vs BYOL), the compute unit you're charged for, and data egress. Both clouds publish current rates; numbers move, so always confirm against the live price list on the day you cost a workload.
1 Oracle OCPU = 2 AWS vCPUs
Oracle's licence model counts on physical cores (with a 0.5 core factor for x86 when licensing into AWS / Azure). On OCI, billing is per-OCPU (one OCPU = one core, two hyper-threads). On AWS EC2, you pay per-vCPU, where a vCPU is one hyperthread. Two AWS vCPUs of compute ≈ one Oracle OCPU of licence consumption. Always normalise to OCPUs when comparing per-hour cost between clouds.
License Included vs BYOL
- AWS RDS for Oracle, SE2 License Included — Oracle licence is bundled into the per-hour instance price. Convenient for short-lived dev / UAT. See aws.amazon.com/rds/oracle/pricing/.
- AWS RDS for Oracle, BYOL (SE2 or EE) — instance is billed at the BYOL rate; you bring (and prove) your own Oracle licence. EE on RDS is BYOL-only.
- AWS RDS Custom for Oracle — BYOL only. EE supported. You manage licence compliance, AWS manages most of the host plane.
- OCI Base / Exadata DB Service — both LI and BYOL exposed for every OCPU shape. BYOL meaningfully reduces the per-OCPU rate (see Oracle's published price list). Universal Credits make BYOL the default for any Oracle-heavy estate.
Egress: the cost that quietly compounds
Both clouds publish per-GB egress to the public Internet from their India regions. Two patterns to watch: (1) inter-AZ data transfer inside a region (AWS charges, OCI does not in the same AD); (2) inter-region replication for DR. For any Data Guard / Active Data Guard topology spanning a primary + standby region, model the egress between primary and standby — it can dwarf compute over time. Always source the live numbers from aws.amazon.com/ec2/pricing/on-demand/ and oracle.com/cloud/price-list/.
5. Compliance, data residency, sovereignty
India's regulatory surface has tightened materially in the past 18 months. Three frames matter for an Oracle DB landing decision:
DPDPA, 2023
Section 8 obligations (notice, consent, security safeguards) apply to personal data regardless of cloud. The platform doesn't relieve the data fiduciary; choose the region that lets you demonstrate residency and access control to the DPB.
RBI Master Direction (BFSI)
The 2023 outsourcing/IT framework requires Indian-resident copies of regulated data and right-to-audit clauses. Both AWS Mumbai/Hyderabad and OCI Mumbai/Hyderabad are in scope; the audit-clause clarity in your MSA matters more than the region label.
SEBI ARPA framework
Capital-market intermediaries face additional reporting + DR-pair obligations. A paired-region DR design is essentially mandatory; both clouds support it in-India.
OCI Sovereign Cloud
Oracle markets sovereign and dedicated-region options for workloads that need isolated control-plane operation. If "sovereignty" is the actual driver — not just data residency — Oracle's Cloud@Customer + dedicated-region path is worth a serious look against AWS commercial regions.
Ogma does not claim CERT-In empanelment or any third-party credential — the table above maps to the published frameworks. We can map your specific workload against each when we scope.
6. When OCI clearly wins for Oracle workloads
You need RAC
OCI is the only public cloud that supports Oracle Real Application Clusters. If your DR / availability design depends on RAC, OCI is the only option.
You need Exadata
Smart Scan, storage cells, Hybrid Columnar Compression — Exadata is OCI-exclusive in the public cloud. If your existing workload is on Exadata on-prem, OCI Exadata Database Service is the natural lift-and-shift target.
Heavy Oracle Cloud-native usage
OAC (Analytics Cloud), OIC (Integration Cloud), Fusion Apps, ERP / SCM Cloud — if your estate already leans on the Oracle Cloud SaaS portfolio, gravity argues for landing the DB next to it.
Licence consolidation under Universal Credits
If you have a meaningful Oracle estate, the Universal Credits programme makes BYOL on OCI the lowest-friction commercial path — and the per-OCPU BYOL rate is the single biggest line-item lever in your contract.
7. When AWS clearly wins for Oracle workloads
Oracle is a minority of your estate
If 70%+ of your stack is on AWS-native services (RDS Postgres, Aurora, S3, Lambda, Kinesis), the gravity well wins. Move the Oracle workload to RDS Custom for Oracle or EC2 BYOL and keep the integrations cheap.
SE2 dev / UAT
RDS for Oracle SE2 License Included is genuinely convenient for low-touch environments — minutes-to-provision, no licence to track, decommission cleanly.
You don't need RAC / Exadata
For a mid-size OLTP workload on SE2 or EE — single instance, Data Guard standby for DR — RDS Custom + a manually-configured standby is operationally viable, and you keep AWS observability + IAM.
Existing standardisation on AWS IAM / VPC / observability
For a CCoE that has standardised on AWS guardrails, breaking out a single Oracle workload to OCI doubles the surface for security review. Sometimes the cheaper path is to stay on AWS even at a moderate compute premium.
8. Decision tree
Walk top-down. The first yes wins.
Do you need RAC or Exadata?
If yes — OCI. There is no equivalent on AWS. Don't try to fake RAC on EC2; it isn't a supported configuration and Oracle support will not back you.
Is sovereignty (not just residency) the actual driver?
If yes — evaluate OCI Dedicated Region / Cloud@Customer. Otherwise both clouds' Indian regions satisfy DPDPA / RBI residency.
Is your estate > 70% AWS-native?
If yes — favour RDS Custom for Oracle (EE BYOL) or EC2 BYOL. Keep observability, IAM and networking standard.
Is the workload small SE2 / dev / UAT?
If yes — RDS for Oracle SE2 License Included on AWS Mumbai. Fastest path. Tear down cleanly.
Are you committing to Oracle Cloud SaaS (Fusion, OIC, OAC) anyway?
If yes — OCI Base DB or Exadata. Universal Credits + Co-location with the SaaS stack tips the math.
None of the above and Oracle EE with Data Guard, real workload?
Both clouds are viable. The deciding factor is your CCoE's existing standardisation; don't over-think it — pick the one your operations team already runs.
9. Five mistakes Indian buyers keep making on this decision
1. "EE on AWS = EC2 only"
RDS Custom for Oracle has supported EE since 2021 and is the right answer for a lot of mid-size EE workloads. Buyers still skip it.
2. Not modelling BYOL math at >50% of estate
If half or more of your Oracle estate is moving cloudward, the BYOL discount on OCI changes the comparison. Always cost both LI and BYOL.
3. Trying to "do RAC on EC2"
RAC is not a supported configuration on AWS. Don't design a critical workload around an unsupported config.
4. Treating "Multi-AZ RDS" as Data Guard
It is a synchronous block-storage mirror, not Oracle Data Guard. Read-on-standby is not exposed. Adjust your DR runbook accordingly.
5. Letting the rep choose the architecture
Both cloud reps will tell you their platform is the right answer. The question is which is right for your estate, your licence position, and your operations posture — and that's an architecture decision, not a sales call.
10. Frequently asked questions
Is RAC really not supported on AWS?
Correct. Real Application Clusters requires shared storage and a clusterware configuration AWS does not expose on RDS / RDS Custom / EC2. Oracle Support's policy is unambiguous on this. If RAC is a hard requirement, OCI is the only public-cloud answer.
What is RDS Custom for Oracle, and why does it matter?
RDS Custom is the "managed-service with OS access" variant of RDS. It launched in 2021 with Oracle support (EE included, BYOL only). It exists because some Oracle workloads need custom OS patches, third-party agents, or DBA-level control of the database host — things plain RDS can't expose. For many AWS-centric shops it is the right answer to "EE on AWS".
Does BYOL on OCI really beat BYOL on AWS economically?
Often, but not always. BYOL on OCI gets a meaningfully reduced per-OCPU rate (see the OCI price list). BYOL on AWS gets you a BYOL instance price that is lower than License Included but is still AWS compute pricing. For BYOL at scale, OCI usually wins per-OCPU. Always model both with your actual workload.
Can I run Exadata workloads on AWS at all?
No. Exadata is hardware-and-software co-engineered by Oracle; it is exposed in the public cloud only via OCI Exadata Database Service and Exadata Cloud@Customer. If your workload depends on Smart Scan or storage-cell features, OCI (or on-prem Exadata) is the path.
Is OCI Hyderabad a true DR pair for OCI Mumbai?
Yes — that is its designed role. OCI exposes Maximum Availability Architecture (MAA) patterns that span the two regions for Exadata and Autonomous. Cross-region egress is billable, so model the DR-traffic cost up front.
What about AWS Hyderabad as a DR region for AWS Mumbai?
Yes — that is the symmetric design. The caveat is that ap-south-2's service catalogue is narrower than ap-south-1; if your DR design uses a service that hasn't yet rolled into ap-south-2, you'll need to redesign or wait. Always confirm against the AWS Regional Services List for the specific services you depend on.
Is there a way to get "Active Data Guard semantics" on AWS?
Not on plain RDS. On RDS Custom or EC2 you can configure Oracle Active Data Guard yourself (with Oracle licensing) but the configuration and operations are your responsibility — AWS does not manage it.
For RBI-regulated BFSI workloads, which cloud is preferred?
Both AWS and OCI satisfy India-resident-copy + right-to-audit obligations in their India regions. The deciding factors are typically: (a) whether RAC / Exadata is required (OCI-only); (b) your existing standardisation; (c) the audit-clause clarity in your MSA. There is no general "RBI prefers X cloud" answer.
Does DPDPA force my Oracle DB to live in India?
Not on its face — DPDPA does not prohibit cross-border transfer to non-blacklisted jurisdictions. But practical compliance (notice, consent, breach reporting, sub-processor management) is much easier when personal data sits in an Indian region. Most enterprises are choosing India-resident for personal data and DR pair.
What's the fastest way to actually compare cost?
Model both clouds against the same workload, with the same licence posture (BYOL on both, or LI on both where supported), normalised to OCPU equivalents. Don't accept rep-built TCO sheets — they will not normalise consistently. Ogma can build the comparison from the published price lists for your specific sizing in one working week.
We'll model your Oracle workload on both, and tell you which lands cheaper
Senior cloud architects model your Oracle stack against OCI Mumbai/Hyderabad and AWS Mumbai/Hyderabad using the live price lists and your licence posture — and tell you, honestly, which one lands cheaper for your estate. Five working days, zero obligation.
Request the assessment or talk to an architect about your specific case →Stay ahead of cyber threats
One short email a week — curated Indian cybersecurity news, Fortinet releases, DPDPA updates. No fluff.
