critical

Amazon Linux 2 EOL

2026-06-30

This deadline passed on 2026-06-30. Affected resources are now in the post-deadline window — clean up before the next enforcement phase.

What is being deprecated?

Amazon Linux 2 reached end of life on 2026-06-30 and should be migrated to Amazon Linux 2023. AWS has published post-EOL AL2 releases, so EOLkits does not equate the date with proof that a specific instance has received no later update; verify the installed release and current AWS support terms.

Next tracked milestone2026-06-30 (-61 days from build date 2026-08-30)
ServiceEC2, EKS, ECS, Elastic Beanstalk
Affected resourcesami|launch-template|container-image
Severitycritical
Migration kital2023-gate (free, MIT)
Primary sourcehttps://aws.amazon.com/blogs/aws/update-on-amazon-linux-2-end-of-life/

The published service dates and status above use the cited provider source. Recheck it before production planning because future dates can change.

Migration checks

When moving away from this runtime or operating-system release, verify these configured concerns in your own workload. A listed concern is not proof that every workload is affected. [provider status source]

  • Standard support ended; remaining update/support behavior must be verified with AWS
  • yum replaced with dnf
  • amazon-linux-extras not available
  • ntpd replaced with chronyd
  • iptables replaced with nftables
  • Python 2 no longer available

Investigate with the free al2023-gate CLI

The MIT-licensed kits have different commands and coverage. Start with local help and the kit README; use fixture or dry-run modes before any command that accepts credentials or an apply flag.

Install from this repository

Keep dependencies isolated and inspect the available commands before running a scan.

python3 -m venv .venv
.venv/bin/pip install -e kits/al2023-gate
.venv/bin/al2023-gate --help

Review exact matches

Treat matches as migration evidence to verify. A static scanner cannot infer live resource counts, traffic, exploitability, or business impact.

Preview a specific migration command

Follow the selected kit's README. Review the diff and run the application's own tests before using an apply or deploy option.

Use your existing release controls

Deploy through your tested CI, canary, monitoring, and rollback process. The scanner does not certify a production rollout.

Need repository evidence for this migration?

Embed this milestone in your README

Drop a milestone badge into a repo that needs this migration review. It links back to the provider-sourced date and bounded checks on this page.

Amazon Linux 2 EOL milestone badge

[![Amazon Linux 2 EOL milestone](https://ntoledo319.github.io/EOLkits/badge/amazon-linux-2-eol.svg)](https://ntoledo319.github.io/EOLkits/migrate/amazon-linux-2-eol/)

Frequently asked questions

What is the next tracked milestone?

2026-06-30. Amazon Linux 2 reached end of life on 2026-06-30 and should be migrated to Amazon Linux 2023. AWS has published post-EOL AL2 releases, so EOLkits does not equate the date with proof that a specific instance has received no later update; verify the installed release and current AWS support terms. [provider status source]

What should I verify before changing the workload?

Validate these configured checks against your code and current upstream documentation: Standard support ended; remaining update/support behavior must be verified with AWS; yum replaced with dnf; amazon-linux-extras not available; ntpd replaced with chronyd; iptables replaced with nftables; Python 2 no longer available. A listed check is not proof that the workload is affected.

Which AWS services does this affect?

EC2, EKS, ECS, Elastic Beanstalk — specifically ami|launch-template|container-image resources.

Is there a free way to migrate?

Yes — the al2023-gate CLI is MIT-licensed and free for local use. Audit v2 is an optional paid repository evidence artifact when its live safety gate is open. EOLkits does not currently sell managed migrations or automated pull requests.