Troubleshooting - AWS Elastic Beanstalk


This chapter provides a table of the most common Elastic Beanstalk issues and describes how to resolve or work around them. Error messages can appear as events on the environment management page in the console, in logs, or on the health page.

If the health of your environment changes to red, try the following:

  • Review recent environment events. Messages from Elastic Beanstalk about deployment, load, and configuration issues often appear here.

  • Review recent environment change history. Change history lists all of the configuration changes made to your environments and includes other information, such as which IAM user made changes and which configuration parameters were set.

  • Pull logs to view recent log file entries. Web server logs contain information about incoming requests and errors.

  • Connect to an instance and check system resources.

  • Roll back to a previous working version of the application.

  • Undo recent configuration changes or restore a saved configuration.

  • Deploy a new environment. If the environment appears healthy, perform a CNAME swap to route traffic to the new environment and continue to debug the earlier one.