AWS Application Load Balancer • Hacker News Board

Re: AWS Application Load Balancer

#131

Post by renaudg » Fri, Aug 12, 2016, 3:18 PM UTC

I'm the process of containerizing an app that includes a Websockets service, and given ECS / ELB limitations we'd just decided to go for Kubernetes as the orchestration layer.

This ALB announcement + the nicer ECS integration could tip the balance though.

Any thoughts on how likely it is that Kubernetes can/will take advantage of ALBs (as Ingress objects I suppose) soon ?

Re: AWS Application Load Balancer

#132

Post by renaudg » Fri, Aug 12, 2016, 5:09 PM UTC

zob_cloud wrote: post #78

bradavogel wrote: post #68

Does anyone know if it (finally) supports sticky websocket sessions?

Yes they do. For a single connection the websocket will always go to the same back end regardless of sticky sessions being enabled. If stickyness is enabled, and the same client creates a new websocket, it will go to the same back end as previous connections.

Where is this documented officially ? There's very little mention of Websockets in the guides, and none at all in the ALB creation wizard, which I didn't find reassuring.

Re: AWS Application Load Balancer

#133

Post by nzoschke » Sat, Aug 13, 2016, 1:46 PM UTC

leetrout wrote: post #29

kookster wrote: post #17

As a heavy ECS user, all I can say is thank you, finally!

What are you using for configuration / orchestration of both the container servers and the tasks? CF? Terraform?

Take a look at Convox as a fast way to bootstrap managing instances, ECS, and load balancers via CloudFormation.

We have ALB working already.

https://github.com/convox/rack/pull/1045

Disclaimer: I work on Convox.

Re: AWS Application Load Balancer

#134

Post by dpessis » Sun, Aug 14, 2016, 3:19 AM UTC

NeckBeardPrince wrote: post #87

Any idea if it's HIPPA compliant?

Customers with an AWS Business Associate Agreement (BAA) can use Application Load Balancer and Classic Load Balancer following the configuration obligations in the BAA. Since Application Load Balancer and Classic Load Balancer are features of an existing HIPAA Eligible Service, Elastic Load Balancing, no changes to the AWS BAA are required.

Re: AWS Application Load Balancer

#135

Post by dexterdog » Sun, Aug 14, 2016, 2:37 PM UTC

lsaferite wrote: post #119

dexterdog wrote: post #63

Earlier quoted context omitted.

If you're using classic (non-VPC) you have to use classic ELBs.

Is there a benefit to using 'Classic'?

If your setup worked under classic you didn't have to setup your VPC and worry about internet gateways and routing all of that stuff. It is better to use VPC and if you have a newer account and in fact you don't even get the option, but some of us have instances that have been running without issue for 7 years and don't want to reconfigure what is working.

Re: AWS Application Load Balancer

#136

Post by iEchoic » Mon, Aug 15, 2016, 1:39 AM UTC

zob_cloud wrote: post #78

bradavogel wrote: post #68

Does anyone know if it (finally) supports sticky websocket sessions?

Yes they do. For a single connection the websocket will always go to the same back end regardless of sticky sessions being enabled. If stickyness is enabled, and the same client creates a new websocket, it will go to the same back end as previous connections.

This isn't working for me, I'm not getting an upgrade header back from the server, it just stalls. Hm.

Did you have to do anything special to get this to work?

Re: AWS Application Load Balancer

#137

Post by iEchoic » Mon, Aug 15, 2016, 2:21 AM UTC

Swennemans wrote: post #126

sjtgraham wrote: post #89

Earlier quoted context omitted.

Because Phoenix has a WS abstraction (Channels) and supports it out of the box.

Yes but isn't one of Elixir's strenghts that it scales very well on a single machine? Why do we need the load balancing?

Every backend architecture should account for having multiple machines. What are you going to do once you get enough traffic that one machine can't handle it?

Re: AWS Application Load Balancer

#138

Post by perfmode » Thu, Aug 18, 2016, 5:27 AM UTC

renaudg wrote: post #129

perfmode wrote: post #105

Earlier quoted context omitted.

Great. I'm looking forward to the day when I can retire my hacky workarounds to facilitate websockets on Elastic Beanstalk.

Out of curiosity, what are these workarounds ?

TCP load balancing with a modified nginx config that forwards the websocket upgrade header

Re: AWS Application Load Balancer

#139

Post by dexterdog » Fri, Aug 19, 2016, 12:03 AM UTC

renaudg wrote: post #130

jeffbarr wrote: post #84

Earlier quoted context omitted.

Small correction to my previous answer, Elastic Beanstalk will support ALB in the very near future.

Are we talking days or weeks ?

I guess weeks because it's still not supported.

Re: AWS Application Load Balancer

#140

Post by chris47493 » Sun, Aug 21, 2016, 12:48 AM UTC

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)

Looks like you can set the Target Group ARN in the LoadBalancers property group now http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuid...