DEV Community

endoflife-ai
endoflife-ai

Posted on • Originally published at endoflife.ai

AWS Quietly Moved Lambda's Runtime Cutoffs to 2027. The Security Clock Didn't Move.

AWS moved the Lambda runtime deprecation wall: functions on Node.js 16/18/20, Python 3.8/3.9, Ruby 3.2, .NET 6 and provided.al2 can now be created until February 1, 2027 and updated until March 3, 2027. But nodejs20.x stopped receiving security patches on April 30, 2026 — the reprieve is operational, not security. Verified against AWS's live docs August 1, 2026.

The verified three-stage schedule

Runtime AWS deprecation (patches stop) Upstream EOL Block function create Block function update
Node.js 20 nodejs20.x Apr 30, 2026 Apr 30, 2026 Feb 1, 2027 Mar 3, 2027
Node.js 18 nodejs18.x Sep 1, 2025 Apr 30, 2025 Feb 1, 2027 Mar 3, 2027
Node.js 16 nodejs16.x Jun 12, 2024 Sep 11, 2023 Feb 1, 2027 Mar 3, 2027
Python 3.9 python3.9 Dec 15, 2025 Oct 31, 2025 Feb 1, 2027 Mar 3, 2027
Python 3.8 python3.8 Oct 14, 2024 Oct 7, 2024 Feb 1, 2027 Mar 3, 2027
Ruby 3.2 ruby3.2 Mar 31, 2026 Mar 31, 2026 Feb 1, 2027 Mar 3, 2027
.NET 6 dotnet6 Dec 20, 2024 Nov 12, 2024 Feb 1, 2027 Mar 3, 2027
OS-only (provided.al2) provided.al2 Jul 31, 2026 Jun 30, 2026* Feb 1, 2027 Mar 3, 2027

What's covered

  • The verified three-stage schedule
  • Why AWS delayed the blocks
  • The trap: the reprieve is operational, not security
  • Where to go: nodejs22.x or nodejs24.x
  • If you genuinely cannot move yet
  • A note on date provenance

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-aws-lambda-runtime-deprecation-2027

Top comments (0)