- Newest
- Most votes
- Most comments
For targets to become healthy, The health check configuraiton needs to be correct and the Load Balancer must be able to connect to the target. Make sure that the security group allows access on the Target port from the LB. Same goes for NACL if ALB is in a different subnet.
You might also want to make sure that the application that is expected to listen in the port and path on which the health check is configured is actually running in the instance.
For eg: If the 'Health check protocol' is 'http' and 'Health check path' is '/' , Try accessing the path directly with 'http://EC2_instance_endpoint/' to make sure that it is running. If not, you need to do the needful to fix that for the health check to succeed.
Double check your configuration, maybe you have mistyped a value which is causing this issue
Relevant content
- AWS OFFICIALUpdated 2 years ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
I have the same question, but the ec2 instance is launched by the Autoscaling process. I can't assign this endpoint in advance?