AWS Lambda — Node.js 18 Runtime
What to do: Migrate functions to Node.js 22 — this one is already past, so patch and update support has stopped.
The end-of-life and deprecation dates that break cloud-native stacks — curated, prioritized, with what to do and why it matters for your SOC 2 / ISO 27001. The ones that hit AWS & serverless teams first.
Last updated: August 4, 2026 · Verified against vendor sources.
What to do: Migrate functions to Node.js 22 — this one is already past, so patch and update support has stopped.
What to do: Already past — kernel patches have stopped. Move EKS node groups to AL2023 / Bottlerocket and move Lambda to AL2023-based runtimes now.
What to do: The AL2-based branches (Go, Java Corretto 8/11/17, Tomcat, Docker/ECS, .NET Core on AL2) are already retired — no more managed platform updates or security patches. Rebuild affected environments on the AL2023 equivalent now.
What to do: Already past — creating new Python UDFs is blocked and existing ones stopped executing. If any of your ETL still calls them, migrate to Lambda UDFs now; a broken pipeline step is worse for an audit trail than the migration itself.
What to do: Community EOL has passed — plan the upgrade to MariaDB 10.11 or 11.4 now. RDS end of standard support for 10.6 follows in August 2026.
What to do: Maintenance mode starts tomorrow — AWS vendors botocore/s3transfer directly into CLI v1, so pip install -U botocore no longer changes what CLI v1 actually uses; only a new CLI v1 release does. If your CVE-patching routine relies on that trick, it stops working. Still worth planning the real move to CLI v2 before v1's end-of-support Jul 15, 2027 (critical fixes only after that, no new services/regions).
What to do: Upgrade control plane and node groups to 1.34+ before Jul 29. Miss it and you're auto-enrolled in Extended Support at 6x the per-cluster-hour cost ($0.10 → $0.60).
What to do: From Jul 30, these close to new customers — Bedrock Agents Classic, Amazon Kendra, Amazon Q Business, 11 SageMaker AI features (Clarify, Debugger, Ground Truth, Model Monitor and more), Cognito Sync, Simple AD. Existing usage keeps working; just don't build anything new on them, and plan a migration path if one is core to your product.
What to do: These branches (all on Amazon Linux 2023) retire Jul 31 — after that, no managed platform updates or security patches. Check the EB console → Configuration → Platform and rebuild any affected environment on a currently supported branch. Beanstalk is exactly where old runtimes get forgotten.
What to do: Plan and test the upgrade to MySQL 8.4 now, or budget for Extended Support (per-vCPU-hour charges start Aug 1, 2026). MySQL 8.0 is the most widely run RDS engine version — the widest blast radius of any EOL this year.
What to do: The OS-only provided.al2 runtime (Go, Rust, any custom runtime on Amazon Linux 2) is deprecated — the AL2 blast radius reaching the runtimes people forget are AL2 underneath. Rebuild on provided.al2023. Security patches have stopped, and container-image functions get no deprecation email at all.
What to do: New PCoIP WorkSpaces signups close Jul 31, 2026; full end of support follows Oct 31, 2027 (HP is retiring the underlying PCoIP/HP Anyware tech). Migrate to the DCV protocol — no extra cost, and existing OS/apps/data carry over via Modify Protocol.
What to do: New WorkSpaces Pools signups close Jul 31, 2026; full end of support follows Dec 31, 2027. Migrate to WorkSpaces Applications — it can import your existing pool image directly.
What to do: Detect closes to new customers Aug 31; existing users keep it. If it's part of the "continuous monitoring" story for a new IoT fleet, enable it before then — don't architect around a feature you can no longer switch on.
What to do: Upgrade Kafka 3.7.x clusters to 3.9.x inside your own maintenance window before Sep 1. The hard part: after end of support, MSK auto-upgrades the cluster to the recommended version at any time, with no notification. An unplanned broker bump is a change you can't point to a change ticket for — own the timing before AWS takes it.
What to do: Move Windows environments to Server 2019 / 2022 / 2025 with IIS 10 before Sep 30. Watch the second wall: default AMIs go inaccessible Jan 15, 2027 — after that, any auto-scaling event, instance replacement or deploy that launches a new instance fails. That's an outage, not just missing patches.
What to do: Console and API access end Oct 7 — your deployed infrastructure keeps running, but you lose Proton's templating/management layer. Migrate service templates to plain IaC (CDK or Terraform) before then.
What to do: Console and resources (endpoints, segments, campaigns, journeys, analytics) go away Oct 30. SMS/voice/push/OTP APIs aren't affected — those already run on AWS End User Messaging. Migrate campaign/journey logic before then.
What to do: Move python3.10 functions to python3.12 or python3.13 — it's the last Amazon-Linux-2-based Python runtime. Patches stop Oct 31; create-block follows Feb 1, 2027.
What to do: Both .NET runtimes deprecate the same day — plan the move to .NET 10 (the LTS successor). Note .NET 9 is container-only with no scheduled create/update block: you're fully on your own after Nov 10.
What to do: The natural upgrade target for anyone who just left 1.33 — plan the jump once, not twice. After Dec 2 it enters (paid) Extended Support.
What to do: Migrate these deprecated runtimes to a current version (Node.js 22, Python 3.12/3.13, Ruby 3.4). Correction: the create/update blocks widely quoted as Aug 31 / Sep 30, 2026 have been pushed by AWS to Feb 1, 2027 / Mar 3, 2027 — more runway, but security patches already stopped, so migrate anyway.
What to do: AWS is retiring Amazon WorkMail — closed to new customers since Apr 30, 2026, full end of support Mar 31, 2027. This is the rare one where the date does delete data: after Mar 31, 2027 the console and all mailbox content (emails, contacts, calendars, attachments) become permanently inaccessible. Export mailboxes and migrate to a third-party mail provider (Zoho Mail, Zoom Mail, Kopano) well before the cutoff.
What to do: Plan ahead — the current Lambda target itself sunsets here, with Lambda deprecation phases following after.
What to do: AWS is retiring re:Post Private — closed to new customers, full decommission Jun 30, 2027. Another one where the date deletes data: all private spaces (questions, answers, knowledge articles) are permanently deleted, no read-only access after. Export via your TAM (final egress deadline Jun 15, 2027) and move to Stack Overflow for Teams / Stack Internal or AWS Builder Center.
What to do: AMS Advanced ends Jun 30, 2027 — no new landing zones after Jun 30, 2026. Your workloads and AWS accounts are not deleted, but the whole managed layer (RFC/change management, AMS patching, monitoring, incident + access management, landing-zone controls) goes away. If a SOC 2 / ISO 27001 control leans on AMS-run patching or change management, you need to re-home it — plan the move to AMS Accelerate, Unified Operations, a partner, or self-managed (target Mar 31, 2027).
What to do: Runway extended from Feb 2027 to Jun 2029 — more time, but Extended Support still bills per vCPU, so plan the upgrade.
No matches. Try a different keyword, or reset the filter to All.
Curated for AWS / serverless / cloud-native teams that must stay compliant. This is a focused radar, not an exhaustive list — dates can change, so always confirm on the vendor source before acting. SunsetSignal is independent and not affiliated with AWS.
The radar is updated weekly. The newsletter brings the new ones straight to you — ranked, with what to do and why it matters for compliance. Free, 5 minutes.
Free forever · 5 min/week · No spam, unsubscribe anytime.