I am trying to learn/use AWS ECS but keep getting
service has reached a steady state.
Followed by:
service (instance i-05873e2a55ecba2f6) (port 32768) is unhealthy in target-group due to (reason Request timed out)
I'm not really sure which info you need to help, but I was using this load balancer across EC2 instances before, but I am replacing those EC2 instances with ones launched through ECS and now I am running into this error.
My cluster is in my default VPC and I am including all 3 subnets (East zone). The security group is my load balancer security group which allows all traffic on ports 40 and 443. I have tried changing security group so that it allows anyone on any port but that doesn't work.
My host port in my task definition is 0 and my container port is 3000 which is what I exposed in Dockerfile.
The healthcheck is just on the target port at path "/"
This is Connection idle timeout setting on ALB, which by default is 60 seconds. can be increased to 4000 seconds. Here is how we can increase it from console. On the Description tab, choose Edit attributes and enter Idle timeout in seconds.
An instance might fail the ELB health check because an application running on the instance has issues that cause the load balancer to consider the instance out of service.
This answer summarize a checklist of points to verify when debugging this kind of error:
Path /healthcheck
in the backend
service /healthcheck
is not 200
3000
or 8080
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With