Exciting! Disappointing that you can't route based on hostname yet, though. I've got 5 ELBs set up to route to different microservices for one app, and because we couldn't do path-based routing before, that's all segmented by hostname. As soon as ALB supports hostname routing, I can collapse those all into a single LB.
AWS Application Load Balancer
31–40 of 140 posts
Re: AWS Application Load Balancer
#32Do ALBs support more than a single SSL certificate?
If the top level is the same you can use a wildcard (*.example.com) cert.
Re: AWS Application Load Balancer
#33This sentence sums up one of my main reasons for appreciating AWS:
The hourly rate for the use of an Application Load Balancer is 10% lower than the cost of a Classic Load Balancer.
They frequently introduce new features while cutting costs.
Re: AWS Application Load Balancer
#34Re: AWS Application Load Balancer
#35Any love for Elastic Beanstalk with these? They seem well matched. Though EB always feels a bit of a red-headed stepchild in the AWS portfolio.
I love elastic beanstalk (minus it's mediocre docs). Agreed here, does elastic beanstalk support setup of new-style elbs (without me doing extensive customization)? When will it if not?
Elastic Beanstalk supports ALB.
Re: AWS Application Load Balancer
#36This looks pretty sweet. The next big thing for api versioning would be header instead of url based routing, looking forward to 'give you access to other routing methods'.
Already has it! "An Application Load Balancer has access to HTTP headers and allows you to route requests to different backend services accordingly."
Edit: On a second read, it's less clear if header based routing is actually available yet...
Re: AWS Application Load Balancer
#37Re: AWS Application Load Balancer
#38We plan to do a blog post about this at some point, but we had the pleasure of seeing exactly how elastic the elb is when we switched Cronitor from linode to aws in February 2015. Requisite backstory: Our api traffic comes from jobs, daemons, etc, which tend to create huge hot spots at tops of each minute, quarter hour, hour and midnight of popular tz offsets like UTC, us eastern, etc. There is an emergent behavior to stacking these up and we hit peak traffic many many times our resting baseline. At the time, our median ping traffic was around 8 requests per second, with peaks around 25x that.
What's unfortunate is that in the first day after setting up the elb we didn't have problems, but soon after we started getting reports of intermittent downtime. On our end our metrics looked clean. The elb queue never backed up seriously according to cloud watch. But when we started running our own healthchecks against the elb we saw what our customers had been reporting: in the crush of traffic at the top of the hour connections to the elb were rejected despite the metrics never indicating a problem.
Once we saw the problem ourselves it seemed easy to understand. Amazon is provisioning that load balancer elastically and our traffic was more power law than normal distribution. We didn't have high enough baseline traffic to earn enough resources to service peak load. So, cautionary tale of dont just trust the instruments in the tin when it comes to cloud iaas -- you need your own. It's understandable that we ran into a product limitation, but unfortunate that we were not given enough visibility to see the obvious problem without our own testing rig.
Re: AWS Application Load Balancer
#39This sentence sums up one of my main reasons for appreciating AWS: The hourly rate for the use of an Application Load Balancer is 10% lower than the cost of a Classic Load Balancer. They frequently introduce new features while cutting costs.
no, they replaced bandwidth costs with new pricing component $0.008 per LCU-hour[1]. If you have 1M idle websocket connections you will pay 100 times more for ALB vs ELB (i.e. $2K/mo vs $18/mo).
Good thing ELB is still here, so you can choose between them depending on your workload.
[1] LCU - Load Balancer Capacity Units
https://aws.amazon.com/elasticloadbalancing/applicationloadb...
Re: AWS Application Load Balancer
#40Exciting! Disappointing that you can't route based on hostname yet, though. I've got 5 ELBs set up to route to different microservices for one app, and because we couldn't do path-based routing before, that's all segmented by hostname. As soon as ALB supports hostname routing, I can collapse those all into a single LB.
The "Hostname" is in the HTTP Header, "Host." The article states that you can route based on Layer 7 headers, so this shouldn't be an issue.