Websockets with AWS and Elastic Beanstalk

Question

I\'m trying to get my websockets working with Amazon Web Service and Elastic Beanstalk (ELB).

I set up a proxy protocol according to: http://docs.aws.amazon.com/Elastic

Answer 1

You should create reverse proxy for Nginx server. You can include this config file in you .ebextensions folder to make Nginx support WS.

Also in the EBS's load balancer configuration change the protocol from HTTP to TCP.

Refer this blog to set up secure WebSocket.

Answer 2

After configuring EC2 Security group your application will work with public IP.

But you still will get issue with using EB URL. To solve this issue, you have to change EB configuration.

1. Go to EB environment page
2. Configuration
3. In Load Balancing section change protocol from HTTP to TCP.

Now you can click EB URL.

Answer 3

This is a very old post but having searched around for answers on this I have found two things you need to do to get websockets on a custom port working with AWS EB.

1. Under the configuration of your EB environment. Go to Software and add an environment variable there. Make sure this is a case sensitive match with your code.

2. Again under the configuration of your EB environment. Go to Load Balancer and add the custom port as a listener.

Make sure you save the new listener under the config and on reload it should be routing websocket traffic on a custom port

Answer 4

I was also looking for possible workaround for this issue, but it's quite easy irrespective of what platform language you are using to develop websocket program on AWS EC2, as am using Node.js nginx in my case, this should work for all supporting platforms.

Configure Security Group

1. In the AWS console, open the EC2 tab.
2. Select the relevant region and click on Security Group.
3. You should have an elasticbeanstalk-default security group if you have launched an Elastic Beanstalk instance in that region for your app.
4. click on Actions button at top, and select Edit inbound rules.
5. here in Type column select All TCP, or you can set some Custom TCP rule as well to listen at your websocket port.
   
   And that's it!

Note: If something is not working, check the "Events" tab in the Beanstalk application / environments and find out what went wrong.

Answer 5

AWS has launched new Application Load Balancer that supports web sockets. Change your ELB to Application Load Balancer and that will fix your issue.

https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/