It looks like AWS has pushed back the dates to 1st November for a whole heap of runtimes, compared to what it looked like this time last month https://web.archive.org/web/20250113143714/https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
Even the old version of the page (retrieved from the Wayback Machine) still gave much more time before blocking function update than is stated in https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/
> Blocking creation of new functions now happens 30 days after deprecation, and blocking updates to existing functions 60 days after.
(e.g. look at Python 3.7 and Node.js 14, where the gap between **Block function create** and **Block function update** used to be almost 14 months on the old page, and is now almost 22 months).
AWS re:Post is community-based, no contributors on here can officially confirm this date. If you are on anything other than Basic support then you're best to log a support call and get it officially confirmed that way (if you have an Enterprise Support Plan then raise it with your Technical Account Manager). Answer from Steve_M on repost.aws
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
aws.amazon.com › blogs › compute › node-js-16-x-runtime-now-available-in-aws-lambda
Node.js 16.x runtime now available in AWS Lambda | Amazon Web Services
May 12, 2022 - This version is in active LTS status and considered ready for general use. To use this new version, specify a runtime parameter value of nodejs16.x when creating or updating functions or by using the appropriate […]
Node.js 16 Runtime Deprecation Date Change
I apologize, but I cannot confirm the specific date change you mentioned for the Node.js 16 runtime deprecation in AWS Lambda. According to the current information available, Node.js 16 is not listed among the supported Lambda runtimes. More on repost.aws
2
0
February 12, 2025End of support for Node.js 16, update to Node.js 20
Is your feature request related to a problem? Please describe. I received an end-of-support notification for Lambda functions using Node.js 16: We are contacting you as we have identified that your AWS Account currently has one or more A... More on github.com
4
January 2, 2024amazon web services - Upgrading AWS Lambda Scripts from Node.js 16.x to 18.x with Minimal Changes - Stack Overflow
I have a collection of 15-20 scripts running on AWS Lambda with Node.js 16.x that perform various operations, including interacting with S3 using functions like copy, headObject, putObject, and get... More on stackoverflow.com
node 16 support
There was an error while loading. Please reload this page · by when it will support node 16 More on github.com
10
August 29, 2022Videos
15:36
Build a REST API using AWS Lambda, API Gateway and NodeJS - YouTube
10:18
How To Import NPM module in AWS Lambda (Node.js) - using Layer ...
09:12
AWS Lambda Tutorial | Node.js Lambda Function to List S3 Bucket ...
08:11
Deploy a Node App to AWS Lambda Using Terraform - YouTube
07:49
Seamlessly Upgrading AWS Lambda Functions to Node.js 18 or 20: ...
AWS
aws.amazon.com › blogs › developer › announcing-the-end-of-support-for-node-js-16-x-in-the-aws-sdk-for-javascript-v3
Announcing the end of support for Node.js 16.x in the AWS SDK for JavaScript (v3) | AWS Developer Tools Blog
August 6, 2025 - Starting January 6, 2025, the AWS SDK For JavaScript (v3) will no longer support Node.js 16.x, which reached end-of-life on September 11, 2023. We encourage you to upgrade to a Node.js Active Long Term Support (LTS) version, which is Node.js ...
Top answer 1 of 2
1
It looks like AWS has pushed back the dates to 1st November for a whole heap of runtimes, compared to what it looked like this time last month https://web.archive.org/web/20250113143714/https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
Even the old version of the page (retrieved from the Wayback Machine) still gave much more time before blocking function update than is stated in https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/
> Blocking creation of new functions now happens 30 days after deprecation, and blocking updates to existing functions 60 days after.
(e.g. look at Python 3.7 and Node.js 14, where the gap between **Block function create** and **Block function update** used to be almost 14 months on the old page, and is now almost 22 months).
AWS re:Post is community-based, no contributors on here can officially confirm this date. If you are on anything other than Basic support then you're best to log a support call and get it officially confirmed that way (if you have an Enterprise Support Plan then raise it with your Technical Account Manager).
2 of 2
0
I apologize, but I cannot confirm the specific date change you mentioned for the Node.js 16 runtime deprecation in AWS Lambda. According to the current information available, Node.js 16 is not listed among the supported Lambda runtimes. The most recent Node.js versions supported by AWS Lambda are Node.js 22, Node.js 20, and Node.js 18.
For Node.js 18, which is the oldest supported Node.js runtime currently listed, the deprecation schedule is as follows:
- Deprecation date: September 1, 2025
- Block function create: October 1, 2025
- Block function update: November 1, 2025
It's important to note that AWS occasionally adjusts deprecation schedules for Lambda runtimes. They may sometimes extend support periods beyond the initial end-of-life dates, particularly if there are security or operational considerations.
If you're currently using Node.js 16 in your Lambda functions, it's recommended to plan for an upgrade to a supported runtime version as soon as possible. This ensures you continue to receive security updates and can take advantage of the latest features. The currently supported Node.js versions (22, 20, and 18) are all running on more recent Amazon Linux versions, which provide better security and performance.
For the most up-to-date and accurate information on Lambda runtime deprecation schedules, it's always best to refer to the official AWS documentation or contact AWS support directly.
**Sources**
Lambda runtimes - AWS Lambda
Building Lambda functions with Node.js - AWS Lambda
Managing AWS Lambda runtime upgrades | AWS Compute Blog
Medium
awstip.com › action-required-aws-lambda-end-of-support-for-node-js-16-0576051e7cb4
[Action Required] AWS Lambda end of support for Node.js 16 | by Adam Fisher / fisher king (@therightstuff) | AWS Tip
February 6, 2024 - Starting on June 12, 2024, Lambda will no longer apply security patches and other updates to the Node.js 16 runtime used by Lambda functions, and functions using Node.js 16 will no longer be eligible for technical support.
GitHub
github.com › aws-solutions › qnabot-on-aws › issues › 673
End of support for Node.js 16, update to Node.js 20 · Issue #673 · aws-solutions/qnabot-on-aws
January 2, 2024 - Starting on June 12, 2024, Lambda will no longer apply security patches and other updates to the Node.js 16 runtime used by Lambda functions, and functions using Node.js 16 will no longer be eligible for technical support.
Author amendlik
AWS
aws.amazon.com › about-aws › whats-new › 2022 › 05 › aws-lambda-adds-support-node-js-16
AWS Lambda adds support for Node.js 16 - AWS
June 9, 2023 - To deploy Lambda functions using Node.js 16, upload the code through the Lambda console and select the Node.js 16 runtime. You can also use the AWS CLI, AWS Serverless Application Model (AWS SAM) and AWS CloudFormation to deploy and manage serverless applications written in Node.js 16.
Stack Overflow
stackoverflow.com › questions › 78415947 › upgrading-aws-lambda-scripts-from-node-js-16-x-to-18-x-with-minimal-changes
amazon web services - Upgrading AWS Lambda Scripts from Node.js 16.x to 18.x with Minimal Changes - Stack Overflow
I have a collection of 15-20 scripts running on AWS Lambda with Node.js 16.x that perform various operations, including interacting with S3 using functions like copy, headObject, putObject, and getObject. Additionally, my scripts utilize AWS services such as Step Functions, Glue, SNS, and Athena.
SoftProdigy
softprodigy.com › home › aws lambda to support nodejs 16: hire a nodejs developer to take advantage
AWS Lambda to Support NodeJs 16
September 18, 2024 - AWS Lambda supports NodeJs 16, which means development companies or developers must specify this version for building or creating functions. Besides this, they must have relevant managed runtime-based images.
Amazon Web Services
amazonaws.cn › en › new › 2022 › amazon-lambda-support-node-js-16-amazon-web-services-china-regions
Amazon Lambda adds support for Node.js 16 in Amazon Web Services China Regions
Amazon Lambda now supports Node.js 16 as both a managed runtime and a container base image in the Amazon Web Services China (Beijing) Region, Operated by Sinnet, and the Amazon Web Services China (Ningxia) Region, Operated by NWCD.
Businesscompassllc
businesscompassllc.com › home
Seamlessly Upgrading AWS Lambda Functions to Node.js 18 or 20: A Step-by-Step Guide - Business Compass LLC®
August 30, 2024 - SIGN UP FOR FREE CONSULTATIONUnderstanding the End of Support for Node.js 16 in AWS Lambda As the tech landscape evolves, so does the need for keeping your cloud functions up-to-date.
Medium
aws.plainenglish.io › navigating-aws-lambdas-end-of-support-for-node-js-16-a-guide-for-cdk-users-75e68a0a5267
Navigating AWS Lambda’s End of Support for Node.js 16: A Guide for CDK ( python ) Users | by AxeMind | AWS in Plain English
February 19, 2024 - Amazon Web Services (AWS) recently announced the end of support for Node.js 16 runtime in AWS Lambda. This shift necessitates action from…
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 › 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.
AWS
aws.amazon.com › blogs › compute › optimizing-node-js-dependencies-in-aws-lambda
Optimizing Node.js dependencies in AWS Lambda | Amazon Web Services
July 13, 2022 - --platform=node and --target=node16.14 are used to indicate the ECMAScript version to target. By using a bundler, you can often compile newer JavaScript features and syntaxes to earlier standards. Since Lambda now supports Node.js 16, set the target to node16.14.
GitHub
github.com › aws › aws-lambda-nodejs-runtime-interface-client › issues › 53
node 16 support · Issue #53 · aws/aws-lambda-nodejs-runtime-interface-client
August 29, 2022 - aws / aws-lambda-nodejs-runtime-interface-client Public · Notifications · You must be signed in to change notification settings · Fork 59 · Star 211 · New issueCopy link · New issueCopy link · Closed · Closed · node 16 support#53 · Copy link · vishal550 ·
Author vishal550
Danielaniszkiewicz
danielaniszkiewicz.com › aws-lambda-node-16
AWS Lambda Node 16 finally there - Daniel Aniszkiewicz blog
Finally, it's done, Node 16 has come to AWS Lambda.
npm
npmjs.com › package › node-lambda
node-lambda - npm
AWS Lambda now supports Node.js 20, Node.js 18 and Node.js 16.
» npm install node-lambda
Published Jan 08, 2024
Version 1.3.0
Author motdotla
Repository https://github.com/motdotla/node-lambda
GitHub
github.com › alixaxel › chrome-aws-lambda › issues › 275
Node 16.x is supported? · Issue #275 · alixaxel/chrome-aws-lambda
May 21, 2022 - I am having the following error when I try to run my lambda with node 16.x, does anyone else get this? "Failed to launch the browser process!\n/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md\n" chrome-aws-lambda Version: ^10.1.0 ·
Published May 21, 2022
Author outaTiME
Stack Overflow
stackoverflow.com › questions › 78422065 › update-nodejs-16-to-nodejs-20-for-aws-lambda
node.js - Update nodejs 16 to nodejs 20 for AWS lambda - Stack Overflow
That will definitely give you Node 20. FROM public.ecr.aws/lambda/nodejs:20 ENTRYPOINT [ "/bin/bash" ]