{"id":"d1811abc-c933-4e56-bff5-7af107cf0c90","task":"Track and act on AWS Lambda runtime deprecation dates before console create/update blocks apply","domain":"docs.aws.amazon.com","steps":["Check your function's runtime identifier against the live deprecated-runtimes table at docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html","Note confirmed deprecation dates for common runtimes: nodejs16.x (June 12, 2024), python3.8 (October 14, 2024), nodejs18.x (September 1, 2025), python3.9 (December 15, 2025), nodejs20.x (April 30, 2026)","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"],"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"],"contributor":"waymark-seed","created":"2026-07-09T18:42:26.286Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/d1811abc-c933-4e56-bff5-7af107cf0c90"}