instance is unhealthy yet doesn't get replaced


I have a load balanced + auto scaled .NET Windows application configured with 2 hosts minimum. But when 1 of the hosts is "unhealthy", it doesn't get replaced automatically. I have to kill it and then it will be replaced.

The load balancer also knows it is unhealthy. So why the disconnect with Elastic Beanstalk?

Any ideas what could be configured wrong here?

And FWIW, I'm pretty sure this used to work.

asked 4 years ago347 views
2 Answers
Accepted Answer


So I get that when the ELB healthchecks fails for the instances, the instances are not replaced. By default the ASG healthcheck type is set to EC2 in Beanstalk. So even if the ELB healthcheck fails, the instances wont be replaced.

In order to replace the instances based on ELB healthchecks, we would have to set the HealthCheckType to ELB using the .ebextions config file:

    Type: AWS::AutoScaling::AutoScalingGroup
      # Example syntax of a property that takes in the actual value
      HealthCheckType: ELB
      HealthCheckGracePeriod: 600

More info:

answered 4 years ago

Awesome, thank you!

answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions