HTTP HEAD Request to Your Elastic Beanstalk URL Fails
"Failed to Perform HTTP HEAD Request to http://<yourapp>.elasticbeanstalk.com:80"
Elastic Beanstalk sends periodic HTTP HEAD requests to the health check URL. This event fires when the health check URL does not respond successfully (with HTTP code 200).
If you receive this event, try one or both of the following:
Make sure that your application’s health check URL exists. For example, if Elastic Beanstalk makes a health check request to
http://healthcheckrocks.elasticbeanstalk.com:80/myapp/index.jsp, ensure that
/myapp/index.jspexists and is accessible. Similarly, for PHP, if you have
http://healthcheckrocks.elasticbeanstalk.com:80/myapp/index.php, make sure that
/myapp/index.phpexists and is accessible. For ASP.NET, if you have
http://healthcheckrocks.elasticbeanstalk.com:80/myapp/default.aspx, make sure that
/myapp/default.aspxexists and is accessible.
Inspect previous events on the Events page in 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. 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>. See CPU Utilization Exceeds 95.00% for more information about this event.