An Edge-Optimized API does use CloudFront to take advantage of POPs close to your calling clients to try to minimize TLS negotiation time, however, ultimately the API itself is still regional and belongs to the AWS region in which you created it. That means that if there is an availability event in that region, your API could be impacted.
To say it another way, Edge-Optimized APIs are not global APIs.
Hope this clarifies.
Thanks for your answer! I always use the URL with the "local"-URL (containing region) to invoke the API (which is shown in the AWS Console). Is there any ("global") Cloud Front URL as well?
- Accepted Answerasked a month ago
- asked 6 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 3 months ago
- How can I resolve the "CNAMEAlreadyExists" error when I create an edge-optimized custom domain name for my API Gateway API?AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 9 months ago
- EXPERTpublished 3 months ago
- EXPERTpublished a month ago