AWS Lambda: runtime deprecation dates for 2027
The Lambda runtimes page lists forecast dates for planning, and says they may change. After deprecation you can still create and update functions for a limited period. The table shows when each is blocked.
| Runtime | Deprecation | Block create | Block update |
|---|---|---|---|
| ruby3.3 | Mar 31, 2027 | Jul 29, 2027 | Aug 31, 2027 |
| nodejs22.x | Apr 30, 2027 | Jul 29, 2027 | Aug 31, 2027 |
| python3.11 | Jun 30, 2027 | Jul 29, 2027 | Aug 31, 2027 |
| java17 (AL2) | Jun 30, 2027 | Jul 29, 2027 | Aug 31, 2027 |
Example
Illustrative. 30 functions: 18 on nodejs22.x, 12 on python3.11. Two groups, one per month, finished well ahead of the April date for Node.js.
Important
The page says Java 8, 11 and 17 have Amazon Linux 2023-based runtimes too, so a move to AL2023 doesn't always need a Java version change. Identifiers differ: java17 runs on AL2, java17.al2023 on AL2023.
Inventory
- ☐ Export runtime per function
- ☐ Check every region
- ☐ Sort by deprecation date
- ☐ Assign an owner per group
Gantt chart — one bar per runtime group →
Source: docs.aws.amazon.com, Lambda runtimes.