Request Header Routing (Using AWS Application Load Balancer)

Question

Level 7 load balancer is more complex and powerful. It checks packets, has access to HTTP and HTTPS headers and (armed with additional information) can do a more reasonable job of distributing the upload to the target.

https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/

I understand that the AWS application load loading platform has access to the HTTP (S) request headers, but I can only see how you can route along the way. Can someone explain how I can route based on the user-agent header. If this is not possible, suggest an alternative AWS method.

Answer 1

Until 2017-05-26, ALB has no header based routing. With the update on 2017-04-05, he has included Host Based Routing . Currently, it only supports routing routes and routes. You can visit here for the latest AWS information.

If you want header-based routing, there are currently no parameters in the ALB. You should have an additional layer similar to the proxy / nginx server. The flow may be something like this.

• Client calling https://example.com
• ALB DNS configured on example.com
• ALB has a target group in which there are nginx instances. Nginx instances are routed to the appropriate load balancer with header information. (for example, if customerId goes to route 123 in ELB 1, then another route to ELB 2)
• Two ELBs have different instances of EC2 attached to it.

But I heard that AWS is working on a header-based routing request.