high

Lambda Node.js 16 create/update restrictions

2027-02-01

163 days until the 2027-02-01 deadline — enough runway to migrate safely.

What is being deprecated?

Node.js 16 Lambda runtime (Amazon Linux 2) deprecated 2024-06-12. Per the AWS Lambda runtime deprecation table, AWS blocks creating new nodejs16.x functions on 2027-02-01 and updating existing ones on 2027-03-03 — the same synchronized Q1-2027 block cluster as nodejs18.x, nodejs20.x, and several Python runtimes.

Next tracked milestone2027-02-01 (163 days from build date 2026-08-22)
ServiceAWS Lambda
Affected resourcesfunction
Severityhigh
Migration kitlambda-lifeline (free, MIT)
Primary sourcehttps://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

The published service dates and status above use the cited provider source. Recheck it before production planning because future dates can change.

Migration checks

When moving away from this runtime or operating-system release, verify these configured concerns in your own workload. A listed concern is not proof that every workload is affected. [provider status source]

  • Upgrade target is nodejs24.x (multi-step: no direct nodejs16.x to nodejs24.x runtime setting)
  • aws-sdk v2 preinstalled on nodejs16.x; nodejs18.x+ bundles AWS SDK for JavaScript v3 instead (require('aws-sdk') stops resolving)
  • Native addons must be rebuilt and tested on the Node.js 24 ABI
  • OpenSSL 3 behavior changes

Investigate with the free lambda-lifeline CLI

The MIT-licensed kits have different commands and coverage. Start with local help and the kit README; use fixture or dry-run modes before any command that accepts credentials or an apply flag.

Install from this repository

Keep dependencies isolated and inspect the available commands before running a scan.

cd kits/lambda-lifeline
npm ci
node bin/cli.mjs --help

Review exact matches

Treat matches as migration evidence to verify. A static scanner cannot infer live resource counts, traffic, exploitability, or business impact.

Preview a specific migration command

Follow the selected kit's README. Review the diff and run the application's own tests before using an apply or deploy option.

Use your existing release controls

Deploy through your tested CI, canary, monitoring, and rollback process. The scanner does not certify a production rollout.

Need repository evidence for this migration?

Embed this milestone in your README

Drop a milestone badge into a repo that needs this migration review. It links back to the provider-sourced date and bounded checks on this page.

Lambda Node.js 16 create/update restrictions milestone badge

[![Lambda Node.js 16 create/update restrictions milestone](https://eolkits.com/badge/lambda-node.js-16-eol.svg)](https://eolkits.com/migrate/lambda-node.js-16-eol/)

Frequently asked questions

What is the next tracked milestone?

2027-02-01. Node.js 16 Lambda runtime (Amazon Linux 2) deprecated 2024-06-12. Per the AWS Lambda runtime deprecation table, AWS blocks creating new nodejs16.x functions on 2027-02-01 and updating existing ones on 2027-03-03 — the same synchronized Q1-2027 block cluster as nodejs18.x, nodejs20.x, and several Python runtimes. [provider status source]

What should I verify before changing the workload?

Validate these configured checks against your code and current upstream documentation: Upgrade target is nodejs24.x (multi-step: no direct nodejs16.x to nodejs24.x runtime setting); aws-sdk v2 preinstalled on nodejs16.x; nodejs18.x+ bundles AWS SDK for JavaScript v3 instead (require('aws-sdk') stops resolving); Native addons must be rebuilt and tested on the Node.js 24 ABI; OpenSSL 3 behavior changes. A listed check is not proof that the workload is affected.

Which AWS services does this affect?

AWS Lambda — specifically function resources.

Is there a free way to migrate?

Yes — the lambda-lifeline CLI is MIT-licensed and free for local use. Audit v2 is an optional paid repository evidence artifact when its live safety gate is open. EOLkits does not currently sell managed migrations or automated pull requests.