Application Load Balancers now Support Advanced Request Routing

Application Load Balancers now support request routing based on standard or custom HTTP headers and methods, query parameters, and source IP addresses. This launch extends the existing support for Host header and path-based routing rules in Application Load Balancers to more fields from HTTP request messages. This richer set of routing criteria enables you to further simplify your application architecture by offloading routing functionality to the load balancer. It can also be used to block unwanted traffic at the load balancer.

With this launch, the rules and conditions are more powerful as well. You can now evaluate multiple conditions in one rule and each condition can specify a match on multiple values. This enables you to set up complex rules to route client requests to your applications. For example, you can forward a request to a particular application based on Host header, path, user-agent header, and query parameter values. You can also consolidate your rules to fewer rules. For example, you can route requests with path values as /signin, /login, or /auth to a login service using just one rule.

The support for advanced request routing is available for existing and new Application Load Balancers at no extra charge in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Northern California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Osaka-Local), Canada (Central), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), EU (Stockholm), South America (São Paulo), China (Beijing), and China (Ningxia).

To learn more, please refer to the demo, the blog post, and the Application Load Balancer documentation.