Lambda Layer
Learn how to add the Sentry Node Lambda Layer to use Sentry in your Lambda functions
The easiest way to get started with Sentry is to use the Sentry Lambda Layer instead of installing @sentry/aws-serverless
with a package manager manually. If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
Before you begin, make sure you have the following:
- You have a Lambda function deployed in AWS.
- You know the AWS region that your function is deployed to.
Add the Sentry Layer by navigating to your Lambda function. Select Layers, then Add a Layer.
Specify an ARN tab as illustrated:
Finally, set the region and copy the provided ARN value into the input.
Choose your setup method based on your Lambda function type:
ESM vs. CommonJS
The setup instructions you should follow depend on how your function runs at runtime, not how it's written in your source code.
- Use CommonJS instructions if your function runs with CommonJS modules (uses
require()
andmodule.exports
at runtime) - Use ESM instructions if your function runs with ES modules (uses
import
/export
at runtime)
Important: Even if you write your code with import
/export
syntax, your function might still run as CommonJS if you're using TypeScript or a build tool that compiles to CommonJS. Check your build output or Lambda runtime configuration to determine which applies to your function.
CommonJS functions support fully automatic setup using environment variables - both SDK initialization and handler wrapping are handled automatically.
ESM functions support automatic SDK initialization via environment variables, but require manual handler wrapping.
In addition to capturing errors, you can monitor interactions between multiple services or applications by enabling tracing.
Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
Set the following environment variables in your Lambda function configuration:
NODE_OPTIONS="--require @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:
For ESM Lambda Functions
You'll also need to manually wrap your handler as shown below:
index.mjs
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
Instead of using environment variables, you can manually initialize the SDK and wrap your handler in code. This approach works for both CommonJS and ESM functions and allows for further customization of the SDK setup.
Note that you don't have to actually install an NPM package for this to work, as the package is already included in the Lambda Layer.
index.js
const Sentry = require("@sentry/aws-serverless");
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,
// 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
});
// Your package imports
exports.handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
It's important to add both, the Sentry.init
call outside the handler function and the Sentry.wrapHandler
wrapper around your function to automatically catch errors and performance data. Make sure that the Sentry.init
call and the import statement are at the very top of your file before any other imports.
First, wrap your handler:
index.mjs
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
Due to ESM limitations, you need to initialize the SDK in a separate file and load it before your function starts.
Create a new file, for example instrument.mjs
to initialize the SDK:
instrument.mjs
import * as Sentry from "@sentry/aws-serverless";
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,
// 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
});
To load the SDK before your function starts, you need to preload the instrument.mjs
by setting the NODE_OPTIONS
environment variable:
NODE_OPTIONS="--import ./instrument.mjs"
That's it — make sure to re-deploy your function and you're all set!
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").