What’s NCR’s data-residency option, AWS Mumbai or Yotta D1 Noida?

Both work, with different trade-offs. AWS Mumbai (ap-south-1) is the default for ~90% of Indian Magento merchants, ~50ms RTT from NCR, very stable, supports every Magento + Hyvä deployment pattern, plus you get S3 / CloudFront / ElastiCache out of the box. Two AZs (ap-south-1a/b/c) for HA. Yotta D1 Noida is the newer, NCR-specific option, commissioned 2022, Tier-IV certified, 30 MW, in Greater Noida. Advantage: on-shore NCR data-residency (sub-5ms intra-DC latency from a Noida or Gurugram office, ideal for govt / PSU / RBI-regulated payment-data merchants who must keep customer + payment data on Indian soil under DPDP + RBI). Disadvantage: Yotta is bare-metal / colocation-style, you manage your own EC2-equivalent, so the dev-ops surface is higher than AWS. We deploy with two patterns: Pattern A = AWS Mumbai primary + S3 cross-region backup (covers 90% of merchants), Pattern B = Yotta D1 Noida primary + AWS Mumbai active-passive standby (for RBI-regulated payment-data merchants). CtrlS Noida + NxtGen Greater Noida are also viable colocation alternatives. AWS Mumbai is included in Standard tier pricing; Yotta D1 setup is a +₹1.5L Enterprise add-on.