4 ms·
ALB seems to be missing a critical part: hostname based routing. Currently all your container services have to be under the same FQDN. Also, the limit of 10 vi
by kennu 10y ago
ALB seems to be missing a critical part: hostname based routing. Currently all your container services have to be under the same FQDN.
Also, the limit of 10 virtual hosts per ALB seems very artificial. Otherwise ALB could be used for virtual hosting of tens or hundreds of low-load container based web services.
I've implemented virtual hosting manually with an Nginx container, but it would be really useful to have ALB do that.
- brandur 10y ago100% agree, especially when there's a reasonable chance that the ALB itself is based on Nginx or some other technologies that has no problem with more complex routing rules or hundreds of virtual hosts. The good news is that it does seem like Amazon is artificially restricting it for now, and intends to further open it up later. From the release blog post [1]: > As you will see in a moment, each Application Load Balancer allows you to define up to 10 URL-based rules to route requests to target groups. Over time, we plan to give you access to other routing methods. [1] https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/ https://aws.amazon.com/blogs/aws/new-aws-application-load-ba...
- nzoschke 10y agoPerhaps we can use CloudFront to do hostname routing.