A healthcare clinic hosts a patient scheduling application on a fleet of Amazon EC2 instances. The instances are registered with a target group for an Application Load Balancer (ALB) and managed by an Auto Scaling group. The clinic's IT team reports that the ALB target group shows all EC2 instances as unhealthy, preventing patients from accessing the portal. However, verification confirms that the web service is running normally on the instances themselves. What is the most likely cause of this behavior?
- AThe security group for the EC2 instances is blocking the outbound return health check traffic because security groups are stateless.
- BThe target group is querying the default port 80 for health checks, and Elastic Load Balancing does not support custom ports for health check configurations.
- CAmazon Route 53 latency-based routing is blocking health checks to the instances because the domain name is not configured with a failover routing policy.
- The security group for the EC2 instances does not allow inbound traffic from the security group of the Application Load Balancer.Cevap
Cevap
The security group for the EC2 instances does not allow inbound traffic from the security group of the Application Load Balancer.
For an Application Load Balancer to successfully perform health checks, the security group assigned to the registered EC2 instances must explicitly permit inbound traffic from the Application Load Balancer's security group on the application's port. Since security groups are stateful, return traffic is automatically allowed.
Adım Adım Çözüm
Anahtar Kavram
Elastic Load Balancing health checks and Security Group rules
Tahmini Süre:1m 0s