NPM Package

Learn how to install the Sentry AWS NPM package to use Sentry in your Lambda functions

In this guide you will learn how to set up the @sentry/aws-serverless SDK for AWS Lambda functions using NPM. We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function. If you need more control over the SDK setup, you can also initialize the SDK in code.

However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, use the Lambda Layer instead.

Before you begin, make sure you have the following:

  • You have a Lambda function deployed in AWS.
  • You're able to deploy dependencies (i.e. node_modules) alongside your function code to AWS Lambda.

In addition to capturing errors, you can monitor interactions between multiple services or applications by enabling tracing. You can also collect and analyze performance profiles from real users with profiling.

Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.

Install the @sentry/aws-serverless SDK using a package manager of your choice:

Copied
npm install @sentry/aws-serverless @sentry/profiling-node

Set the following environment variables in your Lambda function configuration:

Copied
NODE_OPTIONS="--import @sentry/aws-serverless/awslambda-auto"
SENTRY_DSN="https://examplePublicKey@o0.ingest.sentry.io/0"
#  performance
SENTRY_TRACES_SAMPLE_RATE="1.0"
#  performance

To set environment variables, navigate to your Lambda function, select Configuration, then Environment variables:

That's it - make sure to re-deploy your function and you're all set!

To further customize the SDK setup, you can also manually initialize the SDK in your lambda function. The benefit of this installation method is that you can fully customize your Sentry SDK setup in a Sentry.init call.

Create a new file, for example instrument.js to initialize the SDK:

instrument.js
Copied
const Sentry = require("@sentry/aws-serverless");
//  profiling
const { nodeProfilingIntegration } = require("@sentry/profiling-node");
//  profiling

Sentry.init({
  dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",

  // Adds request headers and IP for users, for more info visit:
  // https://docs.sentry.io/platforms/javascript/guides/aws-lambda/configuration/options/#sendDefaultPii
  sendDefaultPii: true,
  //  profiling
  integrations: [nodeProfilingIntegration()],

  //  profiling
  //  performance
  // Add Tracing by setting tracesSampleRate and adding integration
  // Set tracesSampleRate to 1.0 to capture 100% of transactions
  // We recommend adjusting this value in production
  // Learn more at
  // https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
  tracesSampleRate: 1.0,
  //  performance
  //  profiling

  // Set sampling rate for profiling - this is relative to tracesSampleRate
  profilesSampleRate: 1.0,
  //  profiling
});

To load the SDK before your function starts, you need to preload the instrument.js by setting the NODE_OPTIONS environment variable:

Copied
NODE_OPTIONS="--import ./instrument.js"

To set environment variables, navigate to your Lambda function, select Configuration, then Environment variables.

That's it - make sure to re-deploy your function and you're all set!

The instructions above are written for the latest SDK version.

For CommonJS functions: In SDK versions prior to version 8, the @sentry/aws-serverless package was called @sentry/serverless. If you are using an older version, you can follow this guide but replace the package with @sentry/serverless.

For ESM functions: The v7 @sentry/serverless SDK does not work correctly with ESM-based Lambda functions. Please upgrade to the latest SDK and follow the instructions above.

Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").