Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lambda "nodejs20.x" is out, our published Lambda layers should say they support it #4033

Closed
trentm opened this issue May 21, 2024 · 2 comments · Fixed by #4035
Closed

Lambda "nodejs20.x" is out, our published Lambda layers should say they support it #4033

trentm opened this issue May 21, 2024 · 2 comments · Fixed by #4035
Assignees

Comments

@trentm
Copy link
Member

trentm commented May 21, 2024

The "nodejs20.x" lambda layer was released 2023-11-15: https://aws.amazon.com/blogs/compute/node-js-20-x-runtime-now-available-in-aws-lambda/
We need to update the --compatible-runtimes set for our published Lambda layers.

@trentm trentm self-assigned this May 21, 2024
@trentm
Copy link
Member Author

trentm commented May 21, 2024

Note that the Node.js APM agent layer almost certainly already does support the "nodejs20.x" runtime. This change will just update the metadata on the published layers so that it includes "Node.js 20.x" in the "Compatible runtimes" in the AWS Console when editing layers for a Lambda function.

@trentm
Copy link
Member Author

trentm commented May 21, 2024

Internal slack thread initiating this: https://elastic.slack.com/archives/C9A6ANR5Y/p1716184099125189

@trentm trentm changed the title Lambda "nodejs20.x" Is out, our published Lambda layers should say they support it Lambda "nodejs20.x" is out, our published Lambda layers should say they support it May 21, 2024
@trentm trentm mentioned this issue Jun 4, 2024
1 task
fpm-peter pushed a commit to fpm-git/apm-agent-nodejs that referenced this issue Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant