Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Application Load Balancer

aws.amazon.com

Post reply on HN
Print view View original

91–100 of 140 posts

Re: AWS Application Load Balancer

#91

Post by ddollar »

bgentry wrote: post #49
erikcw wrote: post #45

I'm curious if this will Convox to route to multiple services with just a single ALB instead of the historical default of 1 ELB per service. Would be a real cost savings for a micro-services architecture.

It should allow Convox to do that, yes. Although it doesn't appear (from the screenshots) that you can route by Host header, so you'd have to put all your services on the same hostname with different path prefixes to make it work.

We've got some changes coming along these lines. Looks like we might also be able to use CloudFront for hostname routing.

Re: AWS Application Load Balancer

#92

Post by nzoschke »

fred256 wrote: post #90

+1 for CloudFormation support on launch day. +1 for support for ECS services with dynamic ports (finally!) -1 for no CloudFormation support for ECS (To configure an ECS service to use an ALB, you need to set a Target Group ARN in the ECS service, which is not exposed by CloudFormation)

Thanks for sharing the info.

We're using CloudFormation and ECS heavily for Convox, and just can't get off a CloudFormation custom handler (Lambda func) for managing ECS task definitions and services for small reasons like this.

Re: AWS Application Load Balancer

#93

Post by [deleted] »

fred256 wrote: post #90

+1 for CloudFormation support on launch day. +1 for support for ECS services with dynamic ports (finally!) -1 for no CloudFormation support for ECS (To configure an ECS service to use an ALB, you need to set a Target Group ARN in the ECS service, which is not exposed by CloudFormation)

[deleted]

Re: AWS Application Load Balancer

#94

Post by SideburnsOfDoom »

encoderer wrote: post #38

We 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 t…

250 rps in absolute terms is not enormous; and peaks of 25 times relative to base load is not unheard of.

What I think you are indicating is that you have a very unusual thing that ELB is not set up to handle: you go from base to peak load in seconds flat. Or even less? That's interesting and quite unlike the very common model of human visitors to a website ramping up, that ELB is likely designed around.

Re: AWS Application Load Balancer

#95

Post by ricochet007 »

bgentry wrote: post #48
encoderer wrote: post #38

We 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 t…

I was coming here to ask whether pre-warming is still an issue with the ALB service. Maybe jeffbarr can comment on whether that's changed? GCE's load balancer does not use independent VM instances for each load balancer, instead balancing at the network level. So you can instantly scale from 0 to 1M req/s with no issues at all.

bgentry, what do you mean with not needing VM instances? I believe that regardless of the layer at which you load balance (network or application) you still need compute instances to run the LB logic, host the connection tables, etc.

Re: AWS Application Load Balancer

#97

Post by shawn-butler »

Anybody know whether the new ALB handles a client TLS (SSL) when operating in http mode?

I was trying secure an API Gateway backend using a client certificate but found ELB doesn't currently support client side certificates when operating in http mode.

There was this complicated Lambda proxy workaround solution but I gave up halfway through...

https://aws.amazon.com/blogs/compute/using-api-gateway-with-...

Re: AWS Application Load Balancer

#98

Post by jo909 »

ricochet007 wrote: post #95
bgentry wrote: post #48

Earlier quoted context omitted.

I was coming here to ask whether pre-warming is still an issue with the ALB service. Maybe jeffbarr can comment on whether that's changed? GCE's load balancer does not use independent VM instances for each load balancer, instead balancing at the network level. So you can instantly scale from 0 to 1M req/s with no issues at all.

bgentry, what do you mean with not needing VM instances? I believe that regardless of the layer at which you load balance (network or application) you still need compute instances to run the LB logic, host the connection tables, etc.

I think the general difference is, in AWS you provision your own "private" little loadbalancer instance, and they have logic on how little or big (in terms of compute, bandwith etc) this specific loadbalancer needs to be, and resize it constantly for you.

Google runs a single gigantic distributed loadbalancer, and simply adds some rules for your specific traffic to it. All of the compute and bandwith behind this loadbalancer is able to help serving your traffic spike.

Re: AWS Application Load Balancer

#100

Post by brianwawok »

koolba wrote: post #81
pyre wrote: post #79

Earlier quoted context omitted.

You're missing the use-case where you want to use a wildcard certificate and an EV certificate. You can't get an EV wildcard certificate.

> You're missing the use-case where you want to use a wildcard certificate and an EV certificate. You can't get an EV wildcard certificate. Yes that's not possible as EV certs are not issue for wildcards. My counter is that EV certs are for chumps and the entire concept is a scamola. The only justification I'd accept for getting one is proper A/B testing that an EV cert lead to increased revenue. There's no inherent…

EV certs don't stop domain hijacking + cheapo SSL cert attack vector?
Post reply on HN