Which AWS services are affected by Lambda Python 3.9 EOL?

Affected services: AWS Lambda. Affected resource types: function. Source: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

Is there a free tool to migrate off Lambda Python 3.9 EOL?

Yes. python-pivot is an MIT-licensed CLI that scans, codemods, and patches IaC for this deprecation. Paid Audit ($299) and Migration Pack ($1499) tiers add automated reports and PRs.

Lambda Python 3.9 EOL migration guide — deadline 2027-02-01

Q: When is the Lambda Python 3.9 EOL deadline?

The deadline is 2027-02-01. Python 3.9 Lambda runtime (Amazon Linux 2) was deprecated on 2025-12-15 (no further security patches). Per the AWS Lambda runtime deprecation table, AWS blocks creating new python3.9 functions on 2027-02-01 and blocks updating existing ones on 2027-03-03. Functions keep running, but become unpatched and unmodifiable after the block dates. Source: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

What is being deprecated?

Python 3.9 Lambda runtime (Amazon Linux 2) was deprecated on 2025-12-15 (no further security patches). Per the AWS Lambda runtime deprecation table, AWS blocks creating new python3.9 functions on 2027-02-01 and blocks updating existing ones on 2027-03-03. Functions keep running, but become unpatched and unmodifiable after the block dates.

Deadline	2027-02-01 (223 days from build date 2026-06-23)
Service	AWS Lambda
Affected resources	`function`
Severity	high
Migration kit	`python-pivot` (free, MIT)
Primary source	https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.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 2027-02-01 deadline. [source]

distutils module removed
imp module removed
collections.Mapping deprecated
Native wheels may not be available

Migrate with the free `python-pivot` CLI

The MIT-licensed CLI runs the same five-step migration on every deprecation: scan, fix, test, deploy canary, rollback. No AWS credentials needed for the offline fixture run.

Scan your infrastructure

Enumerate every resource still on the deprecated runtime.

pip install python-pivot
python-pivot scan --region us-east-1

Review findings by severity × blast radius

The scan prints a table ordered by how much breaks and how soon.

Apply codemods (dry-run first)

Mechanically-safe rewrites for the breaking changes above. Everything ambiguous is flagged, not auto-changed.

python-pivot apply --dry-run
python-pivot apply

Deploy with a staged canary + auto-rollback

5% → 25% → 50% → 100%, with a CloudWatch-alarm trip reverting instantly.

Want it done for you before 2027-02-01?

Audit PDF

$299

Hash-anchored deterministic report scoring every Lambda Python 3.9 EOL 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: python-pivot 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 2027-02-01 Lambda Python 3.9 EOL 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 2027-02-01 cutoff.

[![Lambda Python 3.9 EOL deadline](https://eolkits.com/badge/lambda-python-3.9-eol.svg)](https://eolkits.com/migrate/lambda-python-3.9-eol/)

Frequently asked questions

When is the Lambda Python 3.9 EOL deadline?

2027-02-01. Python 3.9 Lambda runtime (Amazon Linux 2) was deprecated on 2025-12-15 (no further security patches). Per the AWS Lambda runtime deprecation table, AWS blocks creating new python3.9 functions on 2027-02-01 and blocks updating existing ones on 2027-03-03. Functions keep running, but become unpatched and unmodifiable after the block dates. [AWS source]

What happens if I don't migrate by 2027-02-01?

The breaking changes listed above take effect: distutils module removed; imp module removed; collections.Mapping deprecated; Native wheels may not be available. [source]

Which AWS services does this affect?

AWS Lambda — specifically function resources.

Is there a free way to migrate?

Yes — the python-pivot CLI is MIT-licensed and free for unlimited runs. The paid Audit ($299) and Migration Pack ($1,499) tiers add a hash-anchored report and an automated PR with a CI-failure refund guarantee.

Lambda Python 3.9 EOL