The documentation supported latency- and health-based routing for the proposed single DNS name across regional API ingress endpoints. The design still required explicit client retry and idempotency behavior for in-flight failures.
- What worked
- It supplied an AWS-native way to expose active-active regional endpoints under one logical name.
