ElasticBeanstalk部署Docker化应用超时失败，新手求助

我是AWS ElasticBeanstalk新手，已将应用正确Docker化，本地运行正常，但部署到Beanstalk环境时失败，且尝试获取日志时提示无法检索到日志。部署过程日志如下：

May 1, 2024 00:30:12 (UTC+5:45) INFO Environment health has transitioned from Warning to No Data. None of the instances are sending data.  
May 1, 2024 00:28:13 (UTC+5:45) INFO requestEnvironmentInfo is starting.  
May 1, 2024 00:28:13 (UTC+5:45) WARN Environment health has transitioned from Info to Warning. Application update is aborting (running for 15 minutes). None of the instances are sending data.  
May 1, 2024 00:27:11 (UTC+5:45) ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.  
May 1, 2024 00:27:11 (UTC+5:45) ERROR Failed to deploy application.  
May 1, 2024 00:27:11 (UTC+5:45) ERROR Unsuccessful command execution on instance id(s) 'i-08207a90dfcd27f39'. Aborting the operation.  
May 1, 2024 00:27:11 (UTC+5:45) INFO Command execution completed on all instances. Summary: [Successful: 0, TimedOut: 1].  
May 1, 2024 00:27:11 (UTC+5:45) WARN The following instances have not responded in the allowed command timeout time (they might still finish eventually on their own): [i-08207a90dfcd27f39].  
May 1, 2024 00:16:14 (UTC+5:45) INFO Environment health has transitioned from Ok to Info. Application update in progress on 1 instance. 0 out of 1 instance completed (running for 3 minutes). None of the instances are sending data.  
May 1, 2024 00:13:07 (UTC+5:45) INFO Deploying new version to instance(s).  
May 1, 2024 00:12:44 (UTC+5:45) INFO Environment update is starting.  
May 1, 2024 00:03:15 (UTC+5:45) INFO Added instance [i-08207a90dfcd27f39] to your environment. May 1, 2024 00:03:15 (UTC+5:45) INFO Environment health has transitioned from Pending to Ok. Initialization completed 9 seconds ago and took 2 minutes.  
May 1, 2024 00:03:06 (UTC+5:45) INFO Successfully launched environment: Ecommerce-microservice-env  
May 1, 2024 00:03:04 (UTC+5:45) INFO Application available at Ecommerce-microservice-env.eba-fegjshix.ap-south-1.elasticbeanstalk.com.  
May 1, 2024 00:02:59 (UTC+5:45) INFO Instance deployment completed successfully.  
May 1, 2024 00:01:52 (UTC+5:45) INFO Waiting for EC2 instances to launch. This may take a few minutes.  
May 1, 2024 00:01:36 (UTC+5:45) INFO Created EIP: 43.204.118.11  
May 1, 2024 00:01:21 (UTC+5:45) INFO Created security group named: sg-0e4d88fcccaf16670  
May 1, 2024 00:01:15 (UTC+5:45) INFO Environment health has transitioned to Pending. Initialization in progress (running for 11 seconds). There are no instances.

1. 优先解决日志无法获取问题 #

• 登录EC2控制台定位实例i-08207a90dfcd27f39，检查实例状态是否正常运行、系统状态检查是否通过
• 若实例状态正常，通过SSH或Session Manager连接实例，直接查看关键日志：
  • 容器运行日志：/var/log/docker目录下的文件
  • Beanstalk部署引擎日志：/var/log/eb-engine.log
  • Beanstalk钩子执行日志：/var/log/eb-hooks.log

2. 分析部署超时核心原因 #

从日志看，实例部署超时无响应，常见排查方向：

• 端口映射不匹配：Beanstalk默认检查容器80端口，确认Dockerfile或Dockerrun.aws.json中是否正确暴露80端口，或在Beanstalk环境配置里指定了正确的容器监听端口
• 环境变量缺失：本地运行正常但云端启动失败，可能是依赖的数据库连接、API密钥等环境变量未在Beanstalk环境中配置
• 实例资源不足：当前实例规格太小，容器启动或运行时内存/CPU耗尽导致无响应，可尝试升级实例规格（比如从t2.micro切换到t2.small）
• 安全组规则限制：检查Beanstalk创建的安全组sg-0e4d88fcccaf16670，是否允许容器出站访问（比如拉取镜像、调用外部服务），以及Beanstalk健康检查的入站规则

3. 重新验证Docker配置正确性 #

• 检查Dockerrun.aws.json（若使用）的语法格式是否正确，无拼写或结构错误
• 在本地模拟生产环境：用docker run命令带上所有生产所需环境变量，验证容器能否正常启动并响应请求
• 确认镜像已正确推送至ECR（若使用托管镜像），或Beanstalk能从源码正确构建镜像

4. 重置环境后重新部署 #

• 终止当前故障实例i-08207a90dfcd27f39，让Beanstalk自动创建新实例
• 清理旧应用版本，重新打包部署，确保部署包无冗余文件或错误配置

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