基于Amazon Linux 2 Docker的Elastic Beanstalk多服务部署Nginx配置不生效问题

问题根因&解决方案 #

1. 现有Nginx配置存在语法错误，直接导致启动失败

你上传的nginx.conf存在两处明显语法问题：

• 拼写错误：上游配置upstream serivce_2名称拼写错误，和下方location /api中引用的service_2不匹配，会触发未知上游的报错
• 配置结构错误：你把include conf.d/elasticbeanstalk/*.conf;放在了全局配置块（events、http块之外），该路径下的配置均属于http/server作用域，放在全局位置会直接触发语法错误，导致Nginx无法启动。

2. 平台适配问题

Amazon Linux 2的Elastic Beanstalk Docker平台使用docker-compose部署时，默认不会在宿主机预装Nginx服务，所以你看到nginx.service不存在、未运行是正常现象，需要手动配置安装和自启动。

修复步骤 #

第一步：修正nginx.conf配置

调整后的配置参考如下：

# Elastic Beanstalk Nginx Configuration File
user  nginx;
worker_processes  auto;
error_log  /var/log/nginx/error.log;
pid        /var/run/nginx.pid;
worker_rlimit_nofile    32633;

upstream service_1 {
    server 127.0.0.1:8080;
    keepalive 256;
}

upstream service_2 {
    server 127.0.0.1:5000;
    keepalive 256;
}

events {
    worker_connections  1024;
}

http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    access_log    /var/log/nginx/access.log;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                          '$status $body_bytes_sent "$http_referer" '
                          '"$http_user_agent" "$http_x_forwarded_for"';

    include  conf.d/*.conf;

    map $http_upgrade $connection_upgrade {
            default       "upgrade";
    }

    server {
        listen 80 default_server;
        gzip on;
        gzip_comp_level 4;
        gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;

        access_log    /var/log/nginx/access.log main;

        location / {
            proxy_pass            http://service_1;
            proxy_http_version    1.1;

            proxy_set_header    Connection             $connection_upgrade;
            proxy_set_header    Upgrade                $http_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;
        }

        location /api {
            proxy_pass            http://service_2;
            proxy_http_version    1.1;
            # 建议补全和根路径一致的proxy_set_header配置，避免请求头丢失
            proxy_set_header    Host                   $host;
            proxy_set_header    X-Real-IP              $remote_addr;
            proxy_set_header    X-Forwarded-For        $proxy_add_x_forwarded_for;
        }

        # Include the Elastic Beanstalk generated locations
        include conf.d/elasticbeanstalk/*.conf;
    }
}

第二步：添加配置安装并配置Nginx自启动

在应用源包根目录新增.ebextensions/nginx.config文件，内容如下：

packages:
  yum:
    nginx: []

commands:
  01_enable_nginx_on_boot:
    command: systemctl enable nginx
  02_test_nginx_config:
    command: nginx -t
  03_restart_nginx:
    command: systemctl restart nginx

第三步：确认部署包结构正确

打包时不要嵌套外层目录，确保解压后的结构如下：

├── docker-compose.yml
├── .ebextensions
│   └── nginx.config
└── .platform
    └── nginx
        └── nginx.conf

所有文件权限至少设置为644，避免Nginx读取配置失败。

替代方案（更推荐容器化部署逻辑） #

你也可以直接把Nginx作为第三个服务加入docker-compose.yml，将自定义配置挂载到容器内，仅暴露Nginx的80/443端口到宿主机，无需处理宿主机依赖，适配性更强。

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