[mlhpdx]

Indeed. As another example, I deploy regional API Gateways for "same region" access to service stacks and then tie them into the "global" service using Route53 latency based routing records (one per region). It works nicely to get the best of both worlds.

[myzie]

Nice. I was wondering if r53 latency-based routing would work as an optional add-on to this. I didn't look into it but was thinking it might not work because the latency based routing records are A records that have to point at a fixed IP address right (rather than the function url in my case). But presumably API gateway just gives you hostnames as well so maybe I'm mistaken here?

[mlhpdx]

With API Gateway the resource has a formulaic domain name, but in Route53 that is hidden because you're creating an "alias" record. I'm not sure the same thing would apply to Lambda URLs.

It's not exactly what I'm talking about, which is unfortunately private source, but here's a close public example of something similar (MX records rather than A records). This template get's instantiated in each supported region (a small set, because SES email receiving is only supported in a handful of places):

https://github.com/mlhpdx/email-delivery/blob/master/templat...