AWS Lambda runtime deprecation schedule (2026–2027)

For the runtimes EOLkits tracks: when patches stop, when AWS says it will block creating new functions, when it will block updating existing ones, and the target currently supported by these bounded tools. Each row links the AWS source; future dates can change.

Scan your stack free — find your deprecated runtimes →

Prefer a 10-second check? Paste your config into the free AWS EOL checker. Pasted input is not uploaded; bounded first-party usage events may be sent.

RuntimeDeprecationBlocks createBlocks updateSeverityEOLkits targetSource
nodejs20.x2026-04-302027-02-012027-03-03highnodejs24.xAWS
python3.92025-12-152027-02-012027-03-03highpython3.12AWS
python3.102026-10-312027-02-012027-03-03highpython3.12AWS
nodejs16.x2024-06-122027-02-012027-03-03highnodejs24.xAWS
nodejs18.x2025-09-012027-02-012027-03-03highnodejs24.xAWS
python3.82024-10-142027-02-012027-03-03highpython3.12AWS
nodejs22.x2027-04-302027-06-012027-07-01mediumnodejs24.xAWS
python3.112027-06-302027-07-312027-08-31mediumpython3.12AWS

Functions keep running after deprecation, but become unpatched and — after the block-update date — unmodifiable. Dates reflect the AWS-published schedule and can shift; the linked AWS page is authoritative.

Fixing the upgrade

The upgrade can surface specific errors — removed stdlib modules, the unbundled AWS SDK v2 on Node 18+, native-wheel/ABI breaks. See common migration error fixes, or check the repository evidence report ($299, 30-day money-back) for exact file/line matches, configured references, and a remediation order.

See all tracked AWS deadlines →