AWS Lambda stops patching Python 3.10 today
The python3.10 runtime reaches its deprecation date on 31 October 2026. AWS stops supplying security patches, but gives an unusually long grace period before blocking new functions.
AWS Lambda’s Python 3.10 runtime, python3.10, hits its deprecation date today, 31 October 2026. From here, AWS stops applying security patches and other updates to the runtime, and functions still using it lose eligibility for technical support.
The grace period is longer than usual. Lambda’s standard policy blocks new function creation 30 days after deprecation and blocks updates to existing functions 60 days after that. For Python 3.10, AWS has pushed both dates out: function creation blocks from 29 July 2027, and updates block from 31 August 2027. Existing functions keep running indefinitely either way, just without patches. The replacement, python3.12 on Amazon Linux 2023, is supported until October 2028.
aws lambda update-function-configuration --function-name my-fn --runtime python3.12Why it matters: if you have Lambda functions still on Python 3.10, they will keep running and, unusually, keep accepting updates for a long while yet. But any CVE in the Python interpreter or its Amazon Linux 2 base from today onward goes unpatched on that runtime. Check the Lambda console or Trusted Advisor’s deprecated-runtimes check for anything still on python3.10 and move it to 3.12 on your own schedule rather than AWS’s enforcement deadline.
The caveat: AWS’s own table flags these dates as “provided for planning purposes and subject to change”, so don’t treat July 2027 as fixed in stone.