All posts
Security

Amazon Linux 2 End of Life (June 30, 2026): What on AWS Still Runs It and Where to Move

By

October 25, 2026

8 min read

Amazon Linux 2 stopped receiving standard security updates on June 30, 2026, but it is still inside EC2 fleets, ECS and Batch compute environments, old EKS node groups, retired Elastic Beanstalk platforms, Lambda runtimes and container base images. Where to look, the Lambda dates that matter (Python 3.10 deprecates on October 31), and what changes moving to AL2023.

Amazon Linux 2
AL2023
Lambda
ECS
EKS
Elastic Beanstalk

What ended

Amazon Linux 2 reached end of support on June 30, 2026. Since then it receives no standard security updates, and AWS's advice is to move to Amazon Linux 2023, which is supported until June 2029. Nothing stops running when an operating system goes out of support: that is the problem. Every vulnerability found from July onward stays open on every AL2 machine, and nobody gets an alert saying so.

AL2 is rarely just the EC2 instances you launched yourself. It is underneath managed services, inside container images, and in Lambda runtimes, and each of those has its own schedule. Here is where to look.

Where AL2 hides

Where

Status

What to do

EC2 instances from amzn2-ami-* images

No security updates since June 30, 2026

Rebuild on AL2023 (al2023-ami-*) — there is no in-place upgrade

ECS-optimized AL2 AMIs

Support ended June 30, 2026

Move capacity providers and launch templates to the ECS-optimized AL2023 AMI

AWS Batch ECS compute environments

New AL2 environments blocked since June 30, 2026; existing ones get no updates

Recreate on AL2023 — Batch defaults to it since January 12, 2026

EKS AL2 node AMIs

Last published November 26, 2025; Kubernetes 1.32 was the last version with them

AL2023 or Bottlerocket node groups, which every supported version has

Elastic Beanstalk AL2 platforms

All remaining AL2 branches retired August 6, 2026 — no more maintenance updates

Move to the AL2023 platform branch for your language

Lambda AL2 runtimes

Patched for critical and selected important issues until each runtime's deprecation date

See the dates below

Your own container images FROM amazonlinux:2

Whatever was in the image when it was built

Rebuild on amazonlinux:2023 — nobody will notify you about these

From the Amazon Linux 2 FAQ and the ECS, Batch, EKS, Elastic Beanstalk and Lambda documentation, October 2026.

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

Lambda: the dates that matter

Lambda kept its AL2-based runtimes patched past June for critical and selected important issues, but only until each runtime is deprecated. Deprecated means no more patches and no support; functions keep running, and you can still deploy them for a while longer through the CLI, SAM or CloudFormation.

Runtime

Built on

Deprecated

Then

provided.al2

Amazon Linux 2

July 31, 2026

Move to provided.al2023

python3.10

Amazon Linux 2

October 31, 2026

Move to python3.13 or 3.14

dotnet8

Amazon Linux 2023

November 10, 2026

Move to dotnet10

ruby3.3

Amazon Linux 2023

March 31, 2027

Move to ruby3.4 or ruby4.0

nodejs22.x

Amazon Linux 2023

April 30, 2027

Move to nodejs24.x

python3.11, java8.al2, java11, java17

Amazon Linux 2

June 30, 2027

Newer versions, or the AL2023 builds of Java 8, 11 and 17

From the Lambda runtimes page, October 2026. Node.js 26 and Python 3.15 are in preview, with general availability targeted for November 2026.

To find them: Trusted Advisor's check for Lambda functions using deprecated runtimes lists every affected version, and the Health Dashboard lists the $LATEST versions affected. Container-image functions are the exception — Lambda sends no deprecation notices for them, so check the base images in your Dockerfiles yourself.

What changes on AL2023

  • dnf replaces yum as the package manager (yum still works as an alias), and amazon-linux-extras is gone — packages that came from it come from the main repositories or are installed another way.

  • EPEL is not supported, so anything you pulled from it needs a new source.

  • Instances launched from AL2023 images require IMDSv2 by default, so old scripts or SDKs that call the metadata service without a token stop working — which is the right outcome, but test it.

  • cgroup v2 is the default, which matters for older container runtimes and monitoring agents.

  • There is no in-place upgrade path from AL2. Rebuild from configuration — which is the moment to fix whatever was only ever set up by hand.

Finding everything

  1. EC2: list instances with the image each launched from, and flag image names starting amzn2-ami; Systems Manager Inventory gives the OS version directly where the agent runs.

  2. ECS, Batch and EKS: check the AMI in every launch template, capacity provider and node group — AWS Health planned lifecycle events list affected Batch and ECS resources.

  3. Elastic Beanstalk: any environment on a platform branch whose name includes Amazon Linux 2 rather than AL2023.

  4. Lambda: Trusted Advisor for zip-packaged functions, and a search of your Dockerfiles and ECR images for amazonlinux:2 and AL2 base images.

  5. CI: build agents and AMI pipelines are easy to miss and run with credentials that matter.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.