AWS Elastic Beanstalk
Developer Guide (API Version 2010-12-01)
AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.

Environment Launches but with Issues

"Launched Environment: <environment id>. However, There Were Issues During Launch. See Event Log for Details"

During the launch of a new environment, Elastic Beanstalk monitors the environment to make sure that the application is available. If the application is still unavailable after 6 minutes have passed, the environment enters the ready state; this allows you to take action and make configuration changes. If this event occurs, 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, ensure that /myapp/index.jsp exists and is accessible. Similarly, for PHP, if you have, make sure that /myapp/index.php exists and is accessible. For ASP.NET, if you have, make sure that /myapp/default.aspx exists and is accessible.

  • Make sure you have uploaded a valid .war file or .zip file.

  • Check previous events on the Events page.