1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
It sounds like you probably have some sort of connectivity issue. Make sure all of these are correct
- Security group on ELB is allowing inbound traffic from your clients and oubound traffic to the ASG instances
- Security Group on the ASG instances is allowing inbound traffic on port 80 from the ELB
- NACLs (Network ACLs) for the ELB subnets are allowing traffic to flow both to/from clients as well as to/from the ASG instances
- The ELB is set to public if your clients are coming in over the Internet; private if they're in the VPC or over Peering/VPN/etc
- The ELB subnets have a route table allowing the clients to connect to them
Some tests you can do to narrow down the issue
- From an instance in the same subnet with the same security group as the ELB, try to curl one of the non-working instances directly. If this can connect then you know the security groups on both are working correctly. If it times out there may be a security group or firewall issue. If it gets 'connection refused' then the webserver isn't running/listening correctly
- Try the same thing from an instance in the ELB's subnet. This will test if the NACLs are working correctly
답변함 2년 전