大网数据广告活动
服务器运维问答

Application Load Balancer with AWS Elastic Beanstalk - Target Group

· 52CE 我爱测

I'm using an Application Load Balancer with AWS Elastic Beanstalk After an AWS automatic server update, I was getting a 503 Service Temporarily Unavailable page. (only this, with near zero server load - single instance) [PHP 7.3 …

问题原文

原帖链接 · Ben in CA · CC BY-SA 4.0

I'm using an Application Load Balancer with AWS Elastic Beanstalk

After an AWS automatic server update, I was getting a 503 Service Temporarily Unavailable page. (only this, with near zero server load - single instance)

[PHP 7.3 running on 64bit Amazon Linux/2.9.2 (upgraded from 2.9.1 automatically)]

The Environment itself showed healthy.

I'm using the Application Load Balancer for HTTPS and for future scaling.

It turns out that AWS EB had created a new EC2 instance and terminated the previous instance, and thus there was no instance registered in the Target Group for which the Application Load Balancer was directing to.

How can I configure AWS to have a replacement Elastic Beanstalk EC2 instance be automatically registered in a Target Group for an Application Load Balancer?

已采纳解答

原帖链接 · Ben in CA · CC BY-SA 4.0

This was a while back, and what seems to have been working well for me is adding the applicable Target Group under the Target Group section under the Auto Scaling Groups.

So go to EC2 Console, then at the very bottom of the left menu (currently for me anyways) there's the Auto Scaling Groups. Click on the auto scaling group from the list, and on the Details tab, click Edit, and then add the applicable Target Group.

This then seems to keep them in sync even as the instances change.

So it should look like this: Screenshot

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-01-28)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。