Skip to content

Node.js 16 Runtime Deprecation Date Change

0

Hi, I noticed a change in the AWS Lambda runtime documentation https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

Deprecated runtime Node.js 16 "Block function update" date has changed since last month. It was previously March 31, 2025, but now shows November 1, 2025.

Can anyone confirm if this new date (November 1, 2025) is correct?

asked a year ago2.4K views

2 Answers
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).

EXPERT

answered a year ago

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

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.