Design AWS DR Site Strategy

My production stack already runs in AWS (EC2, RDS, Application Load Balancers, WAF, etc.). I now need a robust secondary site in the Asia-Pacific (Mumbai) region so the business stays online if the primary region fails. DNS-based failover through Route 53 will drive the switch, I’m open to your recommendation on whether a warm or cold standby strikes the right balance, but whichever path we take it must meet a 5–10 minute RTO. RPO is open for your proposal once you see the architecture.

I will grant custom IAM access so you can inspect the current environment. Please focus first on the EC2 fleet, the databases, and the load-balancer/WAF layer when you design the plan. I have already earmarked security hardening and a few performance tweaks, so fold those improvements into the blueprint where relevant.

Deliverables
• Review report of the existing stack, highlighting gaps that affect DR.
• Detailed DR architecture for Mumbai, including justification of warm vs cold, resource mapping, automation flow, and expected RPO.
• Step-by-step implementation playbook with an estimated timeline and monthly cost model.
• List of prerequisites or modifications needed in the live environment before rollout.
• Infrastructure-as-Code (CloudFormation or Terraform) for the DR build, plus runbooks for failover and failback.
• Executed test failover and failback with documented results and any remediation steps.

Acceptance Criteria
The documented procedure must achieve the agreed RTO in a failover test, be fully reversible, and pass an audit of security and performance baselines we outline at project start.

If this scope aligns with your expertise in AWS, high-availability design and IaC, I look forward to your strategy and timeline.