AWS Lambda Problem Node.js & Latest

[SouthBelair]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

We had an existing aws lambda integration in place and noticed that some of our lambdas were missing from the configure list. In trying to correct this we created a new installation and selected an existing project and aws stack, this updated our lambdas to the "latest". The lambdas immediately began producing errors (see below).

Here's what changed:

Lambda ARN changed from arn:aws:lambda:us-east-1:943013980633:layer:SentryNodeServerlessSDK:184 to arn:aws:lambda:us-east-1:943013980633:layer:SentryNodeServerlessSDK:245

NODE_OPTIONS env value changed from -r @sentry/serverless/dist/awslambda-auto to -r @sentry/aws-serverless/cjs/awslambda-auto

We had to disable sentry on all of our node.js lambdas so that they would continue to operate, in order for us to restore sentry reporting we'll have to manually update every lambda with the old layer and NODE_options values, we have hundreds of lambdas.

node:internal/modules/cjs/loader:597
throw e;
^
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './cjs/awslambda-auto' is not defined by "exports" in /opt/nodejs/node_modules/@sentry/aws-serverless/package.json
at new NodeError (node:internal/errors:405:5)
at exportsNotFound (node:internal/modules/esm/resolve:371:10)
at packageExportsResolve (node:internal/modules/esm/resolve:718:9)
at resolveExports (node:internal/modules/cjs/loader:590:36)
at Module._findPath (node:internal/modules/cjs/loader:664:31)
at Module._resolveFilename (node:internal/modules/cjs/loader:1126:27)
at Module._load (node:internal/modules/cjs/loader:981:27)
at internalRequire (node:internal/modules/cjs/loader:174:19)
at Module._preloadModules (node:internal/modules/cjs/loader:1569:5)
at loadPreloadModules (node:internal/process/pre_execution:628:5) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
Node.js v18.20.2
INIT_REPORT Init Duration: 156.91 ms Phase: init Status: error Error Type: Runtime.ExitError
node:internal/modules/cjs/loader:597
throw e;
^
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './cjs/awslambda-auto' is not defined by "exports" in /opt/nodejs/node_modules/@sentry/aws-serverless/package.json
at new NodeError (node:internal/errors:405:5)
at exportsNotFound (node:internal/modules/esm/resolve:371:10)
at packageExportsResolve (node:internal/modules/esm/resolve:718:9)
at resolveExports (node:internal/modules/cjs/loader:590:36)
at Module._findPath (node:internal/modules/cjs/loader:664:31)
at Module._resolveFilename (node:internal/modules/cjs/loader:1126:27)
at Module._load (node:internal/modules/cjs/loader:981:27)
at internalRequire (node:internal/modules/cjs/loader:174:19)
at Module._preloadModules (node:internal/modules/cjs/loader:1569:5)
at loadPreloadModules (node:internal/process/pre_execution:628:5) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
Node.js v18.20.2
INIT_REPORT Init Duration: 634.31 ms Phase: invoke Status: error Error Type: Runtime.ExitError
START RequestId: e2961f2a-10cc-4980-affa-a616efaaa7b8 Version: $LATEST
RequestId: e2961f2a-10cc-4980-affa-a616efaaa7b8 Error: Runtime exited with error: exit status 1
Runtime.ExitError
END RequestId: e2961f2a-10cc-4980-affa-a616efaaa7b8
REPORT RequestId: e2961f2a-10cc-4980-affa-a616efaaa7b8 Duration: 655.34 ms Billed Duration: 656 ms Memory Size: 256 MB Max Memory Used: 15 MB

Expected Result

N/A

Actual Result

N/A

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

[fnfilho]

Having the same problem in production today. Had to rollback and remove our Sentry setup.

[andreiborza]

hello, sorry that you've experienced that.

Version 184 of the Lambda layer was still running the v7 version of our SDK.

While it's not a true fix for your problem, you can continue to use a v7 version of the layer. We specifically published one for 7.116.0, please see https://docs.sentry.io/platforms/javascript/guides/aws-lambda/layer/#lambda-layer-for-v7 for the ARN (unfortunately, you need to modify it yourself for your specific region).

Let me know if that helps at all.

[fnfilho]

Hey @andreiborza,

Thank you for following up. I am still not able to use AWS Lambda Layer.
Ticket #12012 got me confused as well to what is the right configs to set and I can't seem to find a definitive guide and docs of which Lambda Layer Version refers to what SDK Version.

So this is what I've tried so far, all combinations of the following values. Nothing seems to work.

ARNS:
arn:aws:lambda:sa-east-1:943013980633:layer:SentryNodeServerlessSDK:184
arn:aws:lambda:sa-east-1:943013980633:layer:SentryNodeServerlessSDK:240
arn:aws:lambda:sa-east-1:943013980633:layer:SentryNodeServerlessSDK:250
arn:aws:lambda:us-west-1:943013980633:layer:SentryNodeServerlessSDKv7:1

NODE_OPTIONS
--require @sentry/aws-serverless/cjs/awslambda-auto
--require @sentry/aws-serverless/dist/awslambda-auto
--require @sentry/aws-serverless/awslambda-auto

SENTRY_DSN
https://08ed8a1c1939e2689dae86933fd192a0@o359692.ingest.us.sentry.io/XXX

SENTRY_TRACES_SAMPLE_RATE
1.0