Posted On: Mar 30, 2021
You can now configure each path segment of an API Gateway custom domain name to route requests to different APIs. Using multi-level base path mappings, you can implement path-based API versioning and migrate API traffic between APIs according to request paths with many segments.
Starting today, customers can configure custom domain names in both HTTP and REST APIs to route requests to specific APIs using base paths with multiple segments, like /customers/orders/items. This feature enables customers to control which API receives a request according to mappings between an API and any segment of the request path. Customers can use multi-level base path mapping for path-based versioning, where requests sent to /customers/orders/v1/items are routed to a different API than requests sent to /customers/orders/v2/items. Customers can also use this feature to decompose monolithic applications into microservices by sending requests on one path to the monolith, and sending requests on another path with multiple segments to a new microservice.
API Gateway’s support for multi-level base path mapping is generally available in all regions where API Gateway is available. To see where API Gateway is available, review the AWS region table.