![AWS:为什么我的 Elastic Beanstalk 应用程序会定期陷入严重健康状态?](https://linux22.com/image/711773/AWS%EF%BC%9A%E4%B8%BA%E4%BB%80%E4%B9%88%E6%88%91%E7%9A%84%20Elastic%20Beanstalk%20%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%E4%BC%9A%E5%AE%9A%E6%9C%9F%E9%99%B7%E5%85%A5%E4%B8%A5%E9%87%8D%E5%81%A5%E5%BA%B7%E7%8A%B6%E6%80%81%EF%BC%9F.png)
我有几个 EB 实例正在运行默认设置,但尽管他们现在几乎什么都没做(实际上只是运行没有访问者的静态保存页面),他们还是不断陷入严重的健康问题。
这是为什么?我应该担心吗?同样,它们是使用默认EB 设置。
更新
这是访问日志。它们支持@bazze 的假设,即 EB 健康检查正在查看几个常见的 uRL 作为测试,并得到 404 作为回复:
[26/Nov/2017:17:09:46 +0000] "GET / HTTP/1.1" 200 2422 "-" "ELB-HealthChecker/1.0"
[26/Nov/2017:17:09:46 +0000] "HEAD /sql/sql-admin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:47 +0000] "HEAD /sql/phpmyadmin2/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:47 +0000] "HEAD /sql/phpMyAdmin2/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:47 +0000] "HEAD /sql/phpMyAdmin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:47 +0000] "HEAD /db/myadmin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:48 +0000] "HEAD /db/webadmin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:48 +0000] "HEAD /db/dbweb/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:48 +0000] "HEAD /db/websql/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:48 +0000] "HEAD /db/webdb/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:49 +0000] "HEAD /db/dbadmin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:49 +0000] "GET / HTTP/1.1" 200 2422 "-" "ELB-HealthChecker/1.0"
[26/Nov/2017:17:09:49 +0000] "HEAD /db/db-admin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:49 +0000] "HEAD /db/phpmyadmin3/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:49 +0000] "HEAD /db/phpMyAdmin3/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:50 +0000] "HEAD /db/phpMyAdmin-3/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:50 +0000] "HEAD /administrator/phpmyadmin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:50 +0000] "HEAD /administrator/phpMyAdmin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:51 +0000] "HEAD /administrator/db/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:51 +0000] "HEAD /administrator/web/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:51 +0000] "HEAD /administrator/pma/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:51 +0000] "HEAD /administrator/PMA/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:52 +0000] "HEAD /administrator/admin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:52 +0000] "HEAD /phpMyAdmin2/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:52 +0000] "HEAD /phpMyAdmin3/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:52 +0000] "HEAD /phpMyAdmin4/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:53 +0000] "HEAD /phpMyAdmin-3/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
[26/Nov/2017:17:09:53 +0000] "HEAD /php-my-admin/ HTTP/1.1" 404 - "-" "Mozilla/5.0 Jorgee"
答案1
您可以在事件详细信息中看到原因。它说 100% 的请求都失败了,状态代码为 4XX。所以我的猜测是,根据您问题中的信息,这些网站基本上处于闲置状态且未被使用,您只是不时地收到机器人的访问,寻找常见的目录和文件以找到可以破解的东西。检查访问日志,您可以快速确认是否是这种情况。
更新:当为 EB 环境启用增强健康报告且未进行任何操作时,HTTP 请求是环境健康状况的主要来源。在文档中阅读更多相关信息。