1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
You can create a Route 53 health check for each region to validate application health, and configure the request interval and failure threshold according to your use case requirements.
In case of failure, Route53 will remove this record from the routing, while still resolving the DNS lookup using your latency based policy.
Relevant content
- asked 10 months ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago

Thanks. This improves the response time somewhat. I still get 503 for a minute when one region is down. Is there a way to re-architect my application so that detect which regions are responding and only then direct the traffic to them according to latency?
What TTL have you configured for the Route53 record? In order to respond quickly to changes in health status, AWS recommends to specify a TTL of 60 seconds or less when a health check is associated to a latency record. Given your use case requirements, you could reduce this value and combine with a retry policy at the client side.
Thanks. I set the TTL to 60 seconds in the Traffic Flow and it's failing over faster now.