API endpoint types for REST APIs in API Gateway - Amazon API Gateway
Regional API endpoints
This documentation is a draft for private preview for regions in the AWS European Sovereign Cloud. Documentation content will continue to evolve. Published: December 31, 2025.

API endpoint types for REST APIs in API Gateway

Regional API endpoints

A Regional API endpoint is intended for clients in the same Region. When a client running on an EC2 instance calls an API in the same Region, or when an API is intended to serve a small number of clients with high demands, a Regional API reduces connection overhead.

For a Regional API, any custom domain name that you use is specific to the Region where the API is deployed. If you deploy a Regional API in multiple Regions, it can have the same custom domain name in all Regions. You can use custom domains together with Amazon Route 53 to perform tasks such as latency-based routing. For more information, see Set up a Regional custom domain name in API Gateway and Set up an edge-optimized custom domain name in API Gateway.

Regional API endpoints pass all header names through as-is.

Note

In cases where API clients are geographically dispersed, it may still make sense to use a Regional API endpoint, together with your own Amazon CloudFront distribution to ensure that API Gateway does not associate the API with service-controlled CloudFront distributions. For more information about this use case, see How do I set up API Gateway with my own CloudFront distribution?.