- Le plus récent
- Le plus de votes
- La plupart des commentaires
First, check the security group and Network ACL settings on both the ELB and the instance to make sure all the ELBs subnets are able to communicate with the instances in 2b (and that the instance can send replies back)
If that's not the issue, to troubleshoot, disable ELB Healthchecks on the AutoScaling Group (ASG), by changing the healthcheck setting in the ASG to "EC2". This way the instances won't be terminated when they fail healthchecks
Next, after an instance launches, SSH/RDP into it and check the webserver logs to see if any healthchecks from the ELB are making it in at all. You can also launch a test instance in the same subnet(s) as the ELB (using the same security group) to try and send a curl to the instance in 2a to see if the connection can go through
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
Can you share your Target Group health settings and security group info masking any sensitive details? Security group info from the ALB and EC2s