A company runs a web application on Amazon EC2 instances within an Auto Scaling group behind an Application Load Balancer (ALB). The application listens on TCP port 8080. After a new deployment, the ALB marks all instances as unhealthy, causing the Auto Scaling group to repeatedly terminate and launch new instances. Which two actions should a solutions architect take to resolve this issue? (Select two.)
- Configure the health check port in the Application Load Balancer (ALB) target group to use port 8080 or the traffic port.Cevap
- Update the security group of the EC2 instances to allow inbound traffic on port 8080 from the security group of the ALB.Cevap
- CModify the subnet's inbound Network ACL rules to allow TCP port 80, because security groups are stateless and do not automatically allow return health check traffic.
- DChange the target group health check protocol to HTTPS on port 443 to override the custom application port configuration.
- EConfigure an Amazon Route 53 Latency routing policy to route client requests directly to the EC2 instances, bypassing the Application Load Balancer health checks.
Cevap
Configure the health check port in the Application Load Balancer target group to use port 8080 or the traffic port, and update the security group of the EC2 instances to allow inbound traffic on port 8080 from the security group of the ALB.
The correct options are configuring the ALB target group health check port to 8080 and updating the EC2 security group to allow inbound traffic on port 8080 from the ALB. This aligns the load balancer's health check queries with the actual port the application listens on and allows the security group to permit that traffic.
Adım Adım Çözüm
Anahtar Kavram
Auto Scaling and Application Load Balancer Target Group health checks require aligning the target group health check port and security group permissions with the application port.