amazon web services - EC2 unhealthy instance -


elb show instance available in appropriate zone unhealthy. i'm tried make request instance own health-check endpoint received 503.

curl -i public-ip:port/target-healthy-endpoint

http/1.1 503 service temporarily unavailable date: thu, 04 aug 2016 17:25:10 gmt connection: close content-type: text/html; charset=iso-8859-1 

what mean, , should look? on aws doc found this:

solution 3: ensure have healthy instances in every availability zone load balancer configured respond in. verify looking @ healthyhostcount in cloudwatch. 

if indeed pinging public ip address of ec2 instance, , curling health check url returning 503 error code, stop thinking of elb issue. won't find solution in aws docs.

the pure fact ec2 instance responding 503 on it's own accord. sign-in ec2 instance , fix problem until responds 200 status code using curl. may configuration issue http server (iis, apache, other).

as aside, since ec2 instance fronted elb, ec2 instance should reside in private subnet rather public subnet. won't make setup functionally better, hide doesn't need public.


Comments

Popular posts from this blog

Spring Boot + JPA + Hibernate: Unable to locate persister -

go - Golang: panic: runtime error: invalid memory address or nil pointer dereference using bufio.Scanner -

c - double free or corruption (fasttop) -