DeprecationDeskforced-migration deadlines

AWS

AWS Lambda blocks functions on Node.js 18/20 and Python 3.8/3.9 from February 1, 2027

74 days left — Feb 01, 2027

What stops working
From February 1, 2027 Lambda stops letting you create functions on deprecated runtimes including nodejs20.x, nodejs18.x, python3.9, python3.8, ruby3.2, dotnet6 and provided.al2. From March 3, 2027 it also blocks code and configuration updates to existing functions on these and older runtimes (nodejs14.x, python3.7, go1.x, java8). After that you cannot ship a fix to such a function without moving it to a supported runtime.
Who is affected
AWS accounts with Lambda functions still on deprecated runtimes, especially Node.js 18/20 and Python 3.8/3.9.
Official migration path
Change each function to a supported runtime (for example nodejs24.x or python3.13), test, and redeploy. Note nodejs22.x itself is deprecated April 30, 2027.
What the official path does not cover
AWS changes nothing for you: dependency upgrades, breaking language changes, layers and native modules built for Amazon Linux 2, and infrastructure-as-code templates must all be updated and regression-tested per function. Inventory across many accounts and regions is the paid work.
Source
AWS Lambda Developer Guide: Lambda runtimes, deprecated runtimes table (read Nov 17, 2026) · announced 2026 · verified 2026-11-17

Need this done before Feb 01, 2027?

Fixed price, fixed scope, fixed date. From $4,000 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.

Get a fixed-price quote →

One short form (company, email, what runs on this, needed-by). Reply within one business day.

Not ready yet? Get an email when AWS deadlines approach · Firms: get listed for AWS work.

Spotted a wrong date? Report it — corrected with the source within one business day.

← All deadlines