How to implement websocket on elastic beanstalk

The approach you've described for implementing WebSocket support in Elastic Beanstalk is not the recommended or most efficient method. Instead of manually editing the nginx configuration on the EC2 instance, you can use Elastic Beanstalk's built-in configuration capabilities to achieve this more effectively.

To implement WebSocket support in your Elastic Beanstalk environment, you should create a custom nginx configuration file in your application's source code. Here's how you can do it:

1. In your application's root directory, create a folder structure like this: .ebextensions/nginx/conf.d/

2. Inside the conf.d folder, create a new file with a .conf extension, for example, websocket.conf.

3. In this file, add your WebSocket configuration:

location /websocket {
    proxy_pass http://127.0.0.1:8000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_read_timeout 86400s;
    proxy_send_timeout 86400s;
}

Note that I've changed the proxy_pass to use 127.0.0.1 instead of a specific IP address, as this will work regardless of the internal IP assigned to your instance.

4. Make sure to include the following line in your main nginx.conf file (which should also be in the .ebextensions/nginx/ directory if you're providing a custom one):

include conf.d/elasticbeanstalk/*.conf;

This ensures that Elastic Beanstalk will include your custom configuration.

5. Deploy your application. Elastic Beanstalk will automatically apply this configuration to your environment.

By using this method, you're leveraging Elastic Beanstalk's configuration management capabilities. This approach is more maintainable, scalable, and aligns with best practices for Elastic Beanstalk deployments. It ensures that your WebSocket configuration is applied consistently across all instances in your environment, even if you scale up or replace instances.
Sources
Configuring the proxy server - AWS Elastic Beanstalk
Configuring the proxy server - AWS Elastic Beanstalk

Hi,

I would suggest you to read https://engineering.deptagency.com/deploying-a-websocket-application-on-beanstalk to get a detailled solution.

https://binyamin.medium.com/node-websockets-with-aws-elastic-beanstalk-elastic-load-balancer-elb-or-application-load-6a693b21415a is a bit older but quite useful too

Best,

Didier