You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there's a public AWS service that uses Route 53 latency based routing, we could probably leverage that with DNS-over-HTTPS to get a more accurate endpoint selection.
If there's a public AWS service that uses Route 53 latency based routing, we could probably leverage that with DNS-over-HTTPS to get a more accurate endpoint selection.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-latency.html
The text was updated successfully, but these errors were encountered: