Failed to Retrieve Status of Instance <instance id> 4 Consecutive Time(s)

Make sure that your application’s health check URL exists. For example, if AWS Elastic Beanstalk makes a health check request to http://healthcheckrocks.elasticbeanstalk.com:80/myapp/index.jsp, ensure that /myapp/index.jsp exists and is accessible. Similarly, for PHP, if you have http://healthcheckrocks.elasticbeanstalk.com:80/myapp/index.php, make sure that /myapp/index.php exists and is accessbile. For ASP.NET, if you have http://healthcheckrocks.elasticbeanstalk.com:80/myapp/default.aspx, make sure that /myapp/default.aspx exists and is accessbile.

Inspect previous events in the Events tab on the AWS Management Console to ensure that your environment is healthy. For example, if instances of your environments are running at close to 100 percent CPU utilization, they may become unresponsive. AWS Elastic Beanstalk will alert you via an event that reads Instance <instance id> is experiencing CPU Utilization greater than 95.00%. Consider adjusting auto-scaling settings or upgrading to an instance type larger than a <instance type>. For more information, see CPU Utilization Greater Than 95.00%.