Troubleshooting Elastic Beanstalk Logs

• With CloudWatch Logs, each instance in your Elastic Beanstalk environment streams logs to log groups that you can configure to be retained for weeks or years, even after your environment is terminated that help you to troubleshoot issues with your application or configuration files.

• The set of logs streamed varies per environment, but always includes eb-activity.log and access logs from the NGINX or Apache proxy server that runs in front of your application.

• If the CloudWatch Logs Agent (awslogs) stopped pushing the log data to CloudWatch Logs, you can do the following:

  • If logs stopped pushing after a log rotation, check the supported log rotation methods.

  • If logs are only pushed for a short time after the awslogs agent is restarted, check for duplicates in the [logstream] section of the agent configuration file. Each section must have a unique name.

  • If the awslogs.log log file takes up too much disk space, check the log file for errors and correct them.

  • If the log file only contains informational messages, specify a lower logging level for the logging_config_file option in the agent configuration file.