Article
AWS Disaster Recovery to Sovereign Infrastructure via Equinix Fabric
Production on AWS Mumbai, disaster recovery on sovereign Indian infrastructure, joined by a private sub-2ms circuit at Equinix MB4. No public internet, no shared bandwidth, no single point of jurisdictional failure.
You run production on AWS ap-south-1 (Mumbai). Your compliance team needs a disaster recovery site that's not on the same hyperscaler: true infrastructure diversity. Your RTO/RPO requirements demand sub 10ms latency to the DR site, so the public internet won't cut it, and the DR environment must be sovereign: Indian jurisdiction, Indian operations, no foreign law exposure.
Onam Cloud at Equinix MB4 connects to AWS Direct Connect via Equinix Fabric, a software defined interconnection platform that provisions private, low latency Layer 2 connections between any two participants on the Equinix campus.
How Equinix Fabric works
Equinix Fabric is not a VPN tunnel. It's a physical cross connect marketplace: you provision a dedicated Layer 2 circuit between your AWS Direct Connect port, hosted at Equinix Mumbai, and Onam Cloud's network edge, also at Equinix Mumbai. The traffic never leaves the building.
From AWS to sovereign DR in four steps
- 01
Provision Direct Connect
AWS has a physical presence at Equinix Mumbai. Provision a Hosted or Dedicated Direct Connect port through the AWS console.
- 02
Create the Fabric connection
From the Equinix portal, create a virtual connection between your Direct Connect port and Onam Cloud's network service profile: a software defined circuit provisioned in minutes, not weeks.
- 03
Peer the networks
Onam Cloud's edge routers peer with your AWS Virtual Private Gateway over the private VLAN, so your VPCs reach the DR network directly.
- 04
Replicate
Database replication, object sync and Kubernetes state flow over the dedicated circuit at sub-2ms, with Direct Connect pricing instead of internet egress charges.
What runs over the circuit
With sub-2ms latency on a private circuit, you can run near synchronous replication.
- Databases stream to hot standby replicas on Onam Cloud, with an RPO measured in seconds and automatic failover promotion.
- Object storage replicates continuously from AWS S3 to Onam Cloud's Ceph Object Gateway over an S3-compatible API.
- Kubernetes state is backed up with Velero, with GitOps manifests mirrored to a sovereign Git repository, enabling a full cluster rebuild in under 15 minutes.
- VM snapshots use changed block tracking and transfer nightly over the private circuit for full recovery within RTO targets.
What sovereign DR adds
- 01
Jurisdictional diversity: your DR is under Indian law and operated by an Indian entity.
- 02
Vendor diversity: an AWS outage or policy change doesn't affect your DR.
- 03
Key sovereignty: encryption keys for DR data sit in Onam Cloud's sovereign vault, so AWS cannot decrypt your backups even if compelled.
- 04
Regulatory alignment: DR data stays in India, satisfying DPDP Act, RBI and SEBI requirements by architecture.
Equinix Fabric vs a public internet DR path
| Criteria | Public internet | Equinix Fabric |
|---|---|---|
| Latency | 5-15ms, variable | Sub-2ms, deterministic |
| Jitter | Shared, best effort path | Near zero, dedicated path |
| Bandwidth | Best effort | Guaranteed |
| AWS egress cost | Standard internet egress | Direct Connect pricing, materially lower |
Getting started
Setting this up takes coordination across three parties: AWS for the Direct Connect port, Equinix for the Fabric virtual connection, and Onam Cloud for network peering and the DR environment. We handle the Equinix and Onam Cloud sides for you:
- A discovery call to understand your current AWS architecture and RTO/RPO targets.
- A DR architecture designed for your workloads.
- Interconnect provisioning, typically within 3-5 business days.
- Replication setup and validation, with failover drills before you go live.
Run production on AWS. Keep sovereign DR at Onam Cloud. Connect them over Equinix Fabric. True hybrid sovereign disaster recovery, without compromising on latency, security, or compliance.
Built on Onam Cloud
Keep reading
Start the conversation
Let's talk about whereyour infrastructureshould live.
Tell us about your workload, your compliance constraints, and where your users are, and we'll help you figure out the right shape.