AWS Lambda Troubleshooting Framework Log Forwarding from S3

This guide is intended for help troubleshooting logs from the configuration and data collection end. For example: missing logs and/or log messages, unparsed logs, config questions etc. If the issue resides in the UI then there is a separate troubleshooting guide.

Before reading further:

  • Ensure that you have installed and configured a compatible Log Forwarder. You can find a list of the different log forwarding options and how to install New Relic’s various plugins in our documentation here. Troubleshooting for individual forwarders can be found below.
  • Logs in Context is different from Log Forwarding. Setting up Logs in Context for your application simply adjusts your application’s logger to format logs as JSON with New Relic’s logging metadata. This metadata establishes context for your application logs and other features of your New Relic APM agent. Check out our Configure logs in context with APM agents doc for more detailed information.


  • Double check that you have the NewRelic-s3-log-ingestion lambda in your list of lambda functions in AWS.
  • Ensure that the NewRelic-s3-log-ingestion lambda function is using the most recent version. You can check this by navigating to the NewRelic-s3-log-ingestion function in AWS and scrolling down to the “Tags” section. Look for “serverlessrepo:semanticVersion” the value for this tag is the version of the function.
  • Ensure you have the proper configuration set up via Environment Variables.
    • Navigate to the s3 log ingestion lambda in AWS and scroll down to the “Environment Variables” section. Ensure you have a LICENSE_KEY environment variable set.
  • Double check that you’ve added the correct s3 bucket when setting up the trigger for the s3 log ingestion lambda.
    • You can verify this by going to the s3 log ingestion function in Lambda and looking for s3 in the designer section. If you click on the s3 icon you should see your bucket name listed below the designer section.