如何在AWS Elastic Beanstalk中搭配应用负载均衡器弃用Nginx

I totally get where you're coming from—ALB already handles SSL termination and request routing, so keeping Nginx in the middle just adds unnecessary overhead, especially with those CPU spikes and worker_connections errors. Here's how to strip it out while retaining Elastic Beanstalk's auto-config goodness:

1. Use .ebextensions to Customize Environment Configuration #

Elastic Beanstalk lets you override default settings via .ebextensions config files. Start by creating this directory at the root of your application bundle, then add a config file (e.g., 01_disable_nginx.config).

2. Stop and Disable Nginx #

First, we need to ensure Nginx isn't running or set to start on boot. Add these commands to your config file:

commands:
  # Stop Nginx if it's running
  stop_nginx:
    command: "sudo systemctl stop nginx || true"
    ignoreErrors: true
  # Disable Nginx from starting on instance boot
  disable_nginx:
    command: "sudo systemctl disable nginx || true"
    ignoreErrors: true

The || true and ignoreErrors flags prevent deployment failures if Nginx isn't installed for some reason (though it should be for your platform).

3. Redirect ALB Traffic Directly to Your App #

By default, Beanstalk configures ALB to send traffic to Nginx on port 80. We need to update this to point directly to your application's port.

a. Set Your Application's Port #

If your app runs on a specific port (e.g., 8000 for Python/Gunicorn, 3000 for Node.js), define it in the config:

option_settings:
  # Tell Beanstalk which port your app is listening on
  aws:elasticbeanstalk:environment:process:default:
    Port: "8000"
    Protocol: HTTP
  # Update ALB listeners to use the default process (which now targets your app port)
  aws:elbv2:listener:443:
    DefaultProcess: default
  aws:elbv2:listener:80:
    DefaultProcess: default
    ListenerEnabled: 'true'

Make sure your application is configured to listen on 0.0.0.0 (not just localhost) so the ALB can reach it. For example, in Gunicorn you'd use gunicorn --bind 0.0.0.0:8000 app:app.

b. Update Health Checks #

Beanstalk's health checks will now need to target your app's port. The aws:elasticbeanstalk:environment:process:default setting above should handle this, but double-check in the Beanstalk console under Configuration > Load Balancer > Process to confirm the health check path and port match your app.

4. Handle Static Files (If Needed) #

If you were using Nginx to serve static files, you'll need an alternative:

• Host static assets on Amazon S3 and serve them via CloudFront for better performance.
• Configure your application server to serve static files directly (note: this isn't ideal for high traffic, but works for smaller workloads).

5. Deploy and Verify #

1. Package your app with the .ebextensions directory included.
2. Deploy to Elastic Beanstalk.
3. After deployment:
   • SSH into an instance and run sudo systemctl status nginx—it should show as inactive/disabled.
   • Check your ALB's Target Groups in the AWS Console: the target port should match your app's port, and all instances should show as healthy.
   • Test your application to confirm traffic flows directly from ALB to your app without Nginx in the middle.

That's it! You'll eliminate the Nginx overhead and those worker_connections errors while keeping Beanstalk's auto-scaling and management features.

内容的提问来源于stack exchange，提问作者Vadym Ozarynskyi