We do also have CloudFront - which can front dynamic content, and even integrate with Lambda@Edge to serve responses. But at that point it's not really acting a

We do also have CloudFront - which can front dynamic content, and even integrate with Lambda@Edge to serve responses. But at that point it's not really acting as a load balancer. R53 + Geo DNS | Latency Based DNS | Traffic Manager + Application Load Balancer | Network Balancer is definitely our go-to recommendation and it's used by a variety of customers to handle traffic globally. Route53 supports ALIAS records, so everything still works at the root of your domain (e.g. mydomain.com). Failover is handled with DNS health checks that propagate more quickly than the cascading BGP routing updates that power alternatives such as anycast, as well as avoiding breakage of other in-flight connections due to route table disruption. R53 + Health Checks is what we use for www.amazon.com. I'm curious - what would you prefer to see in an alternative?