AWS Elastic Bean Stalk

Send AWS Elastic Bean Stalk logs to Timber

Timber integrates with AWS Elastic Beanstalk through it's ebextensions feature, enabling you to forward log files to to Timber.


  1. In your shell add the TIMBER_API_KEY and TIMBER_SOURCE_ID environment variables:

    eb setenv TIMBER_API_KEY={{your-api-key}} TIMBER_SOURCE_ID={{your-source-id}}

    (you can also do this in the AWS EB console itself by following these instructions.)


  2. Add the 01_timber.config file to your .ebextensions folder:

    mkdir -p .ebextensions
    curl -o .ebextensions/01_timber_install.config
  3. Package your source bundle and upload it to AWS Elastic Beanstalk as usual.


The 001_timber.config file installs FluentBit as a log forwarder. As such, please refer to FluentBit's configuration documentation on the various options available. All of the options can be modified in the "/tmp/td-agent-bit.conf": section of the 001_timber.config file.


Which log files should I forward?

This depends on your use-case, but we've typically found the following log files to be valuable:

  1. Apache HTTP Access Log - /var/log/httpd/access_log

  2. Apache HTTP Error Log - /var/log/httpd/error_log

  3. Nginx Access Log - /var/log/nginx/access.log

  4. Nginx Error Log - /var/log/nginx/error.log

  5. Nodejs - /var/log/nodejs/nodejs.log

  6. Passenger - /var/app/support/logs/passenger.log

  7. Rails - /var/app/support/logs/production.log

Please refer to the AWS docs on Elastic Beanstalk log locations for a comprehensive guide and list. If you are unsure, it is recommended that you SSH onto the server to locate the actual paths of your log files.


Because the AWS Elastic Bean Stalk integration relies on Fluent Bit we recommend reviewing the following troubleshooting guides: