🌐
AWS
aws.amazon.com › blogs › compute › node-js-22-runtime-now-available-in-aws-lambda
Node.js 22 runtime now available in AWS Lambda | Amazon Web Services
November 23, 2024 - You can now develop AWS Lambda ... use. Node.js 22 includes a number of additions to the language, including require()ing ES modules, as well as changes to the runtime implementation and the standard library....
🌐
AWS
aws.amazon.com › about-aws › whats-new › 2024 › 11 › aws-lambda-support-nodejs-22
AWS Lambda adds support for Node.js 22 - AWS
November 22, 2024 - AWS Lambda now supports creating serverless applications using Node.js 22. Developers can use Node.js 22 as both a managed runtime and a container base image, and AWS will automatically apply updates to the managed runtime and base image as they become available.
Discussions

lambda: Node 22
Describe the feature Node 22 is now the active LTS version. Node 20 is already is already in maintenance mode. Node 18 is still in maintenance mode, but will end-of-life in 6 months. https://github... More on github.com
🌐 github.com
6
October 31, 2024
📊Tracking: [Lambda/Custom Resources] upgrade to Node 22
Overview Node 20, which is currently in its Maintenance LTS phase, is slated to reach its End of Life on 2026-04-30, as indicated on https://nodejs.dev/en/about/releases/. Our aim is to provide CDK users with sufficient preparation time ... More on github.com
🌐 github.com
4
February 28, 2025
Lambda Node 22 coldstart latency regression - defer loading of node:http
I've checked AWS Forums and StackOverflow. I've searched for previous similar issues and didn't find any solution. When I updated to Node 22 on Lambda using the AWS Javascript SDK V3 last year, it added at least 50 ms to my coldstart times. More on github.com
🌐 github.com
12
March 2, 2025
Node 20 / 22 schedule
Please provide a public estimated nodejs/any runtime release schedule and update the community with changes as they occur. Nodejs20 is available on lambda and elsewhere. Two years ago I requested t... More on github.com
🌐 github.com
12
February 28, 2024
People also ask

How Can I Find All Lambda Functions Using Node.js 20 Across Multiple AWS Accounts?
CloudQuery Platform syncs Lambda function data into a SQL database, letting you query all accounts and regions with a single SQL statement. The query filters the `aws_lambda_functions` table where `Runtime` equals `nodejs20.x`. See the detection section above for the full setup and queries.
🌐
cloudquery.io
cloudquery.io › home › blog › aws lambda node.js 20 end of life: upgrade to node.js 22 before april 2026
AWS Lambda Node.js 20 EOL: Upgrade to Node.js 22 | CloudQuery Blog
Does the Node.js 20 EOL Affect Lambda Layers Too?
Lambda Layers themselves don't have a runtime setting, but they do contain code that runs under whatever runtime the function uses. If a Layer includes native modules compiled for Node.js 20, those binaries will need to be recompiled for Node.js 22. Rebuild and republish any Layers with native dependencies after upgrading. Ready to identify your affected Lambda functions? Get started with CloudQuery Platform to get visibility across your AWS infrastructure. Contact us or join our community to connect with other users.
🌐
cloudquery.io
cloudquery.io › home › blog › aws lambda node.js 20 end of life: upgrade to node.js 22 before april 2026
AWS Lambda Node.js 20 EOL: Upgrade to Node.js 22 | CloudQuery Blog
Can I Skip Node.js 22 and Go Straight to Node.js 24?
You can, but be aware that Node.js 24 removes support for callback-based Lambda handlers. If your functions use the `callback` parameter pattern, you will need to rewrite them to use `async/await`. For most teams, upgrading to Node.js 22 first is the lower-risk path.
🌐
cloudquery.io
cloudquery.io › home › blog › aws lambda node.js 20 end of life: upgrade to node.js 22 before april 2026
AWS Lambda Node.js 20 EOL: Upgrade to Node.js 22 | CloudQuery Blog
🌐
Amazon Web Services
docs.aws.amazon.com › aws lambda › developer guide › lambda runtimes
Lambda runtimes - AWS Lambda
For more information, see Migrating AWS Lambda functions from the Go1.x runtime to the custom runtime on Amazon Linux 2 ... All supported Lambda runtimes support both x86_64 and arm64 architectures. Lambda provides managed runtimes for new language versions only when the release reaches the long-term support (LTS) phase of the language's release cycle. For example, for the Node.js release cycle
🌐
Aws-news
aws-news.com › article › 01935112-4f15-ffc9-bbe1-1a10ea3f1157
Node.js 22 runtime now available in AWS Lambda
AWS Lambda now supports Node.js 22 runtime, offering developers new language features like experimental ES module loading, WebSocket support, and TypeScript sy...
🌐
GitHub
github.com › aws › aws-cdk › issues › 31964
lambda: Node 22 · Issue #31964 · aws/aws-cdk
October 31, 2024 - import { Runtime } from 'aws-cdk-lib/aws-lambda' import { NodejsFunction } from 'aws-cdk-lib/aws-lambda-nodejs' new NodejsFunction(this, 'Example', { runtime: Runtime.NODEJS_22_X })
Author   w3nl
🌐
Nobackspacecrew
speedrun.nobackspacecrew.com › blog › 2025 › 07 › 21 › the-fastest-node-22-lambda-coldstart-configuration.html
The Fastest Node 22 Lambda Coldstart Configuration - Speedrun
For evaluating coldstarts I ran the code in us-east-2 on Node 22 with 512 MB memory and the arm64 architecture. The code was compiled to javascript and used the AWS Lambda node runtime: nodejs:22.v48 with ARN: arn:aws:lambda:us-east-2::runtime:ccd522aa46eeddade4be388ba28af972761953cf91d2745b89d3215c05b412c2 and build date: 2025-06-20T00:28:43.000Z.
Find elsewhere
🌐
GitHub
github.com › aws › aws-cdk › issues › 33626
📊Tracking: [Lambda/Custom Resources] upgrade to Node 22 · Issue #33626 · aws/aws-cdk
February 28, 2025 - Lambda runtime: NODEJS_LATEST is not recommended, use NODEJS_22_X instead Node 22 is supported in CDK but is not the default for Lambda as not every region supports 22 yet (at the time of writing 18 is the default), however Node 22 is available ...
Author   SimonCMoore
🌐
CloudQuery
cloudquery.io › home › blog › aws lambda node.js 20 end of life: upgrade to node.js 22 before april 2026
AWS Lambda Node.js 20 EOL: Upgrade to Node.js 22 | CloudQuery Blog
November 24, 2025 - TL;DR: AWS Lambda Node.js 20.x reaches end-of-life on April 30, 2026, after which security patches stop and you progressively lose the ability to create or update functions on this runtime.
🌐
Amazon Web Services
docs.aws.amazon.com › aws lambda › developer guide › building lambda functions with node.js
Building Lambda functions with Node.js - AWS Lambda
You can run JavaScript code with Node.js in AWS Lambda. Lambda provides runtimes for Node.js that run your code to process events. Your code runs in an environment that includes the AWS SDK for JavaScript, with credentials from an AWS Identity and Access Management (IAM) role that you manage.
🌐
GitHub
github.com › aws › aws-sdk-js-v3 › issues › 6914
Lambda Node 22 coldstart latency regression - defer loading of node:http · Issue #6914 · aws/aws-sdk-js-v3
March 2, 2025 - Node 22 exhibits 50 additional ms of coldstart time over Node 20 in the Lambda environment. ... Runs 1 and 2 show the baseline without the AWS SDK.
Author   perpil
🌐
ECR Public Gallery
gallery.ecr.aws › lambda › nodejs
AWS Lambda/nodejs - Amazon ECR Public Gallery
Amazon ECR Public Gallery is a website that allows anyone to browse and search for public container images, view developer-provided details, and see pull commands
🌐
Amazon Web Services
docs.aws.amazon.com › aws lambda › developer guide › lambda managed instances › lambda managed instances runtimes › node.js runtime for lambda managed instances
Node.js runtime for Lambda Managed Instances - AWS Lambda
Maximum concurrencyBuilding functions for multi-concurrencyNode.js 22 callback-based handlersShared /tmp directoryLoggingRequest contextInitialization and shutdownDependency versionsPowertools for AWS Lambda (TypeScript)Next steps · For Node.js runtimes, Lambda Managed Instances uses worker threads with async/await-based execution to handle concurrent requests.
🌐
AWS
aws.amazon.com › blogs › compute › node-js-24-runtime-now-available-in-aws-lambda
Node.js 24 runtime now available in AWS Lambda | Amazon Web Services
November 25, 2025 - The Lambda Runtime for Node.js 24 includes the following changes relative to the Node.js 22 and earlier runtimes.
🌐
Amazon Web Services
amazonaws.cn › en › new › 2024 › amazon-lambda-adds-support-for-node-js-22
Amazon Lambda adds support for Node.js 22 in Amazon Web Services China Regions
3 weeks ago - Amazon Lambda now supports creating serverless applications using Node.js 22 in the Amazon Web Services China (Beijing) Region, operated by Sinnet, and the Amazon Web Services China (Ningxia) Region, operated by NWCD.
🌐
GitHub
github.com › aws › apprunner-roadmap › issues › 238
Node 20 / 22 schedule · Issue #238 · aws/apprunner-roadmap
February 28, 2024 - Please provide a public estimated nodejs/any runtime release schedule and update the community with changes as they occur. Nodejs20 is available on lambda and elsewhere. Two years ago I requested that we have some basic insight into thes...
Author   SirJamesBrown
Top answer
1 of 2
3

The AWS CLI doesn't provide a means for converting a lambda ARN or a lambda runtime ARN into a corresponding Node.js version.

If you want this information just report it to CloudWatch via console.log(process.version), and then inspect the log for a test run.

For example:

export const handler = async (event) => {
  console.log('NODE_VERSION', process.version)
  const response = {
    statusCode: 200,
    body: process.version,
  };
  return response;
};

Produces logs like:

INIT_START Runtime Version: nodejs:20.v22   Runtime Version ARN: arn:aws:lambda:us-west-2::runtime:b41f958332022b46328145bcd27dce02539c950ccbf6fde05884f8106362b755
2024-05-07T18:44:28.717Z    47f2299a-daec-4586-b97f-fd7c0ebf66b4    INFO    NODE_VERSION v20.12.0
2 of 2
1

The Lambda runtime version does not correlate to the Node.js minor version, so for example the runtime version "nodejs 18.v24" does not mean it should be using Node.js version 18.24.x, rather it's the 24th time aws has updated the nodejs18 runtime.

The issue is likely being caused by a dependency, normally a patch version wouldn't cause an issue like that so it might be a rare issue that's difficult to find

As a temporary solution it looks you can set the lambda runtime manually and stop it from updating it so you can have some time to find the issue then update the runtime version. There is some information in the aws documentation about this:

In the rare event that a new runtime version is incompatible with your existing function, you can roll back its runtime version to an earlier one. This keeps your application working and minimizes disruption, providing time to remedy the incompatibility before returning to the latest runtime version.

I'm assuming your lambda function is currently using the $LATEST version by default, and must be automatically updating the runtime version as well, so these instructions might be what you need

If you're using the Auto runtime version update mode, or you're using the $LATEST runtime version, you can roll back your runtime version using the Manual mode. For the function version you want to roll back, change the runtime version update mode to Manual and specify the ARN of the previous runtime version.

You can get the ARN of the working version from the labda logs you posted with the question

These are documentation pages I found this info from

  • https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html
  • https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html#runtime-management-controls
  • https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html#runtime-management-identify
🌐
Amazon Web Services
docs.aws.amazon.com › aws lambda › developer guide › document history
Document history - AWS Lambda
The following table describes the important changes in each release of the AWS Lambda Developer Guide before June 2018.