Understand that deprecation does not stop already-running functions — it only triggers later "block function create" and "block function update" dates, which vary per runtime and must be checked individually
Plan around the underlying Amazon Linux 2 end-of-life on June 30, 2026, which forces deprecation of several AL2-based runtimes (Java 8/11/17, Python 3.10/3.11, provided.al2) independent of language-version timelines
Update IaC (SAM/CloudFormation/CLI) pipelines to target a supported runtime before the update-block date, since console blocking and CLI/IaC blocking can occur on different dates
Known gotchas
Deprecation date, block-create date, and block-update date are three distinct milestones per runtime — don't treat "deprecated" as "shut off"
AWS CLI/SAM/CloudFormation can sometimes still update function code after the console UI blocks manual updates — verify current behavior per runtime rather than assuming parity
The AL2 OS end-of-life (June 30, 2026) drives some runtime deprecations independently of the language version's own EOL — check both triggers
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?