AWS ELB adds support for Host-based routing on Application Load Balancer

This is probably the least "shiny" thing AWS has announced, but to me it's the biggest one yet. I can finally have a single LB for all of prod. This is probably the first thing they've announced that I will be using on day one. It is kind of unbelievable that a feature such as this took so flipping long to add. But hey, it's here now.

Have been waiting for this for awhile. However, is needing to &quot;warm up&quot; the load balancer to deal with sudden spikes still an issue? This was a deterrent to going all-in on the ALB despite other benefits (SSL termination, etc.)<p>Also, wondering if there any obvious cons (perhaps performance?) to using one ALB to handle multiple routes vs. separating them.

This excites me more than a machine learning or speech-to-text API because I&#x27;ll actually use this feature a lot.

With this announcement, is there still any benefit in having cloudfront in front of alb if you don&#x27;t do any caching? I assume that aws has less latency on their internal network, but would love to see some numbers.

Does that mean - If I have 4 ec2 instances sitting behind an ALB, I can target and hit 1 of the 4 ec2 instances if need be? For eg. debugging purposes?

Does this mean that ALB&#x2F;ELB supports SNI now? Or they only allow you to do this with subdomains under a wildcard cert?

Am I able to use a single ALB across many Elastic Beanstalk applications?