Question

A financial services company runs a latency-sensitive trading API on an Application Load Balancer in two AWS Regions (us-east-1 and eu-west-1). Global clients connect over TCP with long-lived, encrypted sessions and cannot tolerate connection resets during a regional failure. The API responses are fully dynamic and non-cacheable. The company wants clients to always use a single fixed set of static IP addresses and needs sub-minute automatic regional failover. Which edge design best meets these requirements?

Accepted Answer

Deploy AWS Global Accelerator with two endpoint groups (one per Region), each containing the regional ALB endpoint, and configure health checks for automatic failover.

Answer

Deploy Amazon CloudFront with an origin group referencing both regional ALBs and enable origin failover with a caching policy that disables caching.

Answer

Use Route 53 latency-based routing with health checks pointing at each regional ALB and publish the ALB DNS names to clients.

Answer

Deploy an NLB in each Region with Elastic IPs and use Route 53 failover routing to switch between the two static IP sets.