so would a websocket-based application be better off using NLB?
ALBs are great for WS and can term SSL for WSS. Just use "HTTP" and "HTTPS" protos on the target groups and it'll work. It's a bit confusing but it works.
AWS Network Load Balancer
61–70 of 122 posts
Re: AWS Network Load Balancer
#62Earlier quoted context omitted.
ELB's Application Load Balancer (ALB) supports HTTP/2 termination. More in the original launch announcement: https://aws.amazon.com/blogs/aws/new-aws-application-load-ba... and https://aws.amazon.com/elasticloadbalancing/details/#details
http2 termination is not very useful, most people want ELB -> backend instances.
in case anyone is confused about this sub-thread:
"""
Application Load Balancers provide native support for HTTP/2 with HTTPS listeners. You can send up to 128 requests in parallel using one HTTP/2 connection. The load balancer converts these to individual HTTP/1.1 requests and distributes them across the healthy targets in the target group using the round robin routing algorithm. Because HTTP/2 uses front-end connections more efficiently, you might notice fewer connections between clients and the load balancer. Note that you can't use the server-push feature of HTTP/2.
"""
( http://docs.aws.amazon.com/elasticloadbalancing/latest/appli... )
Re: AWS Network Load Balancer
#63Earlier quoted context omitted.
I doubt. Unfortunately, CloudFormations lags severely behind...
CloudFormation, CodeDeploy, and ECS all support NLB today :) I used the console to create the simple demo though, so I don't have a template to recreate it. Sorry!
Good as I'm tired spending days writing Customer Resources!
Re: AWS Network Load Balancer
#64Earlier quoted context omitted.
It sounds like NLB passes through source IP - does that mean outbound flows are through the IGW?
There must be some magic happening somewhere, because otherwise outgoing packets would have the wrong source address.
You can use direct server return to manipulate the Ethernet frames so that packets don't travel back through the load balancer on the way to the parent switch.
Re: AWS Network Load Balancer
#65This was discussed a couple of times recently, but answers seemed contradictory. ELB requires pre-warming if you expect sudden high load. But do ALB and NLB? [1] https://news.ycombinator.com/item?id=15085863 [2] https://news.ycombinator.com/item?id=14052079
Forum post answer, so not 100% official, but it is from an AWS employee. "Yes, while you should see performance increases on ALB in general, for major traffic surges we still recommend a pre-warm" https://forums.aws.amazon.com/message.jspa?messageID=746774
I would trust what @collmmac (https://news.ycombinator.com/user?id=colmmacc) is writing above, as he is a Senior Principal on NLB: https://www.linkedin.com/in/colmm1/
Re: AWS Network Load Balancer
#66Re: AWS Network Load Balancer
#67I was so excited before I realized this wouldn't terminate http(s) traffic.
An IP anycast based load balancer ALB would be nice.
Re: AWS Network Load Balancer
#68How does failover across zones work?
The blog post says there's one static ip per zone. I suppose www.mydomain should have multiple A records each pointing to an elastic ip in a zone. What happens when one zone entirely fails? Does it need a DNS change at this point? Or does the NLB have a different IP with which it can do BGP failover?
Re: AWS Network Load Balancer
#69I was just wondering if this is something purely developed inside amazon or is it backed by an ADC like NetScaler or F5. does anyone know any detail ? I'm assuming that classic load balancer is some third-party or old framework and this is something amazon developed internally.
Re: AWS Network Load Balancer
#70Earlier quoted context omitted.
There must be some magic happening somewhere, because otherwise outgoing packets would have the wrong source address.
You can use direct server return to manipulate the Ethernet frames so that packets don't travel back through the load balancer on the way to the parent switch.
That generally requires config on the serving hosts, which wasn't mentioned in the setup. I think I saw a reference to adding hosts with a different port number than the service port as well. For people in EC2-VPC (not classic), all their traffic is going through an Amazon NAT anyway, perhaps this new service is setting up translations there. (Note all the references to VPC, and never a mention of EC2-classic)