Lambda Python 3.10 deprecation: Oct 31, 2026
THE TAKEAWAY
Key dates for python3.10Find affected functionsUpgrading to Python 3.14Sources
Last checked against AWS documentation:
Key dates for python3.10
| Phase | Date | What AWS says happens |
|---|---|---|
| Deprecation | Oct 31, 2026 | AWS may no longer apply security or other updates; no technical support; you can no longer create or update python3.10 functions in the Lambda console (CLI, SAM and CloudFormation still work). |
| Block function create | Jul 29, 2027 | New python3.10 functions can't be created. Existing ones can still be updated via CLI/SAM/CloudFormation. |
| Block function update | Aug 31, 2027 | Existing python3.10 functions can no longer be updated. After this you can't switch back to the deprecated runtime. |
Existing functions keep running: AWS says you can continue to invoke them indefinitely, but they run "as-is" and may hit issues such as certificate expiry. There is no extended-support fee for Lambda.
Find affected functions
AWS lists affected functions in the Health Dashboard (Scheduled changes) and the Trusted Advisor deprecated runtimes check. Or by CLI, in each Region:
aws lambda list-functions --function-version ALL \ --query "Functions[?Runtime=='python3.10'].[FunctionName,Version]" --output text
Drop --function-version ALL to see only $LATEST. Paste output into the checker.
Upgrading to Python 3.14
- python3.14 is supported until Jun 30, 2029 (create blocked Jul 31, 2029, update blocked Aug 31, 2029).
- python3.10 runs on Amazon Linux 2; python3.12 and later run on Amazon Linux 2023. Rebuild native dependencies and layers for the new OS rather than reusing AL2 builds.
- Python 3.12 removed
distutils; Python 3.13 removed several old standard-library modules (cgi,crypt,telnetlib, ...). - Tip from a reader on r/Python: check your
requestsandurllib3pins before you change the runtime. python3.12 and later run on Amazon Linux 2023, which AWS documents as featuring OpenSSL 3, and urllib3 2.x supports OpenSSL 1.1.1 and newer. Releases of requests before 2.30 block urllib3 2.x, so an old pin leaves you on urllib3 1.26.x, which is no longer maintained; move to requests 2.31 or later and read the urllib3 v2 migration guide first. We found no AWS or urllib3 source saying urllib3 1.x itself fails on OpenSSL 3, so the pin issue above is the part we can document. - Tip from a reader on r/Python: watch Pydantic v1. One reader called Pydantic v1 compatibility the biggest headache in their upgrade. Pydantic documents that the V2 package still provides access to the V1 API through
pydantic.v1(for examplefrom pydantic.v1 import BaseModel), and recommends migrating to V2 when you can. Pydantic V2 also depends onpydantic-core, a compiled library, and Pydantic warns that pip installs wheels built for your local platform, which may not work on Lambda; its compiled file name varies with the OS, CPU architecture and Python version. Build your zip or layer for the Lambda runtime's Python version and architecture (x86_64orarm64), and see Pydantic's AWS Lambda guide for thepip install --platformcommand and a check for theno module named pydantic_core._pydantic_coreerror. - Change the runtime identifier (
Runtime: python3.14in SAM/CloudFormation,runtime = "python3.14"in Terraform). Container-image functions need a new base image instead. - AWS recommends testing first and using versions and aliases for rollback.
Full list: what breaks moving off python3.10. Python 3.11 is on AL2 too and is deprecated Jun 30, 2027, so it is a short stop.
Sources
- AWS Lambda runtimes: supported runtimes, deprecation policy, runtime use after deprecation ↗
- AWS Lambda: Building with Python (runtime table, OS) ↗
- Python 3.12 what's new ↗
- Python 3.13 what's new ↗
- urllib3 v2 migration guide (OpenSSL 1.1.1+ requirement, 1.26.x status) ↗
- requests 2.30.0 release notes (urllib3 2 support) ↗
- requests 2.31.0 release notes ↗
- Amazon Linux 2023: OpenSSL 3 ↗
- Pydantic migration guide (pydantic.v1 namespace) ↗
- Pydantic: installing for AWS Lambda (pydantic-core, platform and Python version) ↗
FAQ
When is Lambda python3.10 deprecated?
Oct 31, 2026. Function creation is blocked Jul 29, 2027 and function updates Aug 31, 2027, per the AWS Lambda runtimes table.
Will my python3.10 functions stop working?
No. AWS says you can continue to invoke them indefinitely, but they no longer get security updates or technical support and may break over time.
Can I still deploy python3.10 after Oct 31, 2026?
Not from the Lambda console. Through the AWS CLI, SAM or CloudFormation you can still create functions until Jul 29, 2027 and update them until Aug 31, 2027.
What should I upgrade to?
python3.14, supported until Jun 30, 2029. It runs on Amazon Linux 2023 instead of Amazon Linux 2, so rebuild native dependencies.
More guides
- EKS extended support cost calculator
- RDS & Aurora extended support pricing
- RDS MySQL 8.0 end of support
- RDS PostgreSQL end-of-support dates
- Lambda runtime deprecation schedule
- ElastiCache for Redis OSS end of support
- OpenSearch & Elasticsearch end of support
- OpenSearch extended support fees from Nov 7, 2026
- RDS MariaDB 10.6 end of support (Dec 31, 2026)
- EKS 1.31 end of extended support (Nov 26, 2026)
- RDS PostgreSQL 14 end of standard support (Feb 28, 2027)
- Lambda .NET 8 deprecation (Nov 10, 2026)
- Amazon Neptune 1.1/1.2 end of life (Dec 4, 2026)
- RDS MySQL 8.4.5/8.4.6/8.4.7 end of standard support (Oct 31 & Nov 30, 2026)
- EKS 1.34 end of standard support (Dec 2, 2026)
- ElastiCache Redis OSS 6 end of standard support (Jan 31, 2027)
- Aurora PostgreSQL 14 end of standard support (Feb 28, 2027)
- Infrastructure Composer standalone console shutdown (Dec 7, 2026)