What breaks when IMDSv1 Enforcement reaches end of life?

IMDSv1 requests fail; Must use IMDSv2 with session tokens; SSM agent must be updated. Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html

Which AWS services are affected by IMDSv1 Enforcement?

Affected services: EC2. Affected resource types: instance|launch-template. Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html

Is there a free tool to migrate off IMDSv1 Enforcement?

EOLkits provides cited migration guidance and paid Audit / Migration Pack tiers for this deprecation.

IMDSv1 Enforcement migration guide — deadline 2025-12-31

Q: When is the IMDSv1 Enforcement deadline?

The deadline is 2025-12-31. IMDSv1 access will be blocked by default on new instance launches. Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html

What is being deprecated?

IMDSv1 access will be blocked by default on new instance launches.

Deadline	2025-12-31 (-174 days from build date 2026-06-23)
Service	EC2
Affected resources	`instance\|launch-template`
Severity	high
Primary source	https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html

Every fact on this page is taken from the cited AWS / upstream source above. EOLkits ships no claim without a primary source.

Breaking changes

The following changes take effect at or before the 2025-12-31 deadline. [source]

IMDSv1 requests fail
Must use IMDSv2 with session tokens
SSM agent must be updated

Want it done for you before 2025-12-31?

Audit PDF

$299

Hash-anchored deterministic report scoring every IMDSv1 Enforcement finding by severity × blast-radius, with a roll-forward roadmap and cost-of-not-fixing estimate. Delivered by email in 5 minutes. 30-day money-back guarantee.

Order Audit — $299

Run the free scan first · see a sample →

Migration Pack

$1,499

A real PR opened on your repo: EOLkits codemods + IaC patches + canary plan + rollback. Auto-refund if your CI fails within 7 days.

Get Migration Pack — $1,499 How it works

Not ready to migrate yet?

Get a reminder before the 2025-12-31 IMDSv1 Enforcement deadline — plus a heads-up on the next AWS EOL that hits your stack. No spam, one email per relevant deadline.

Free. Unsubscribe anytime.

Embed this deadline in your README

Drop a deadline badge into any repo still affected. It links back to this page, so your team — and anyone reading the repo — stays aware of the 2025-12-31 cutoff.

[![IMDSv1 Enforcement deadline](https://eolkits.com/badge/imdsv1-enforcement.svg)](https://eolkits.com/migrate/imdsv1-enforcement/)

Frequently asked questions

When is the IMDSv1 Enforcement deadline?

2025-12-31. IMDSv1 access will be blocked by default on new instance launches. [AWS source]

What happens if I don't migrate by 2025-12-31?

The breaking changes listed above take effect: IMDSv1 requests fail; Must use IMDSv2 with session tokens; SSM agent must be updated. [source]

Which AWS services does this affect?

EC2 — specifically instance|launch-template resources.

IMDSv1 Enforcement