You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, we have published the preview AWS Lambda Python 3.15 runtime. You can use it to build and deploy Python 3.15 Lambda functions in both deployment formats:
Managed runtime (ZIP): select the python3.15 runtime when deploying your function code as a .zip archive.
Container image (OCI): build and deploy your function using the preview base image public.ecr.aws/lambda/python:3.15-preview.
⚠️Public preview - not for production use. Preview runtimes are provided for feedback and testing only, and should not be used for production workloads. They are not covered by AWS Technical Support and are not eligible for the Lambda SLA. The purpose of preview runtimes is to gather feedback prior to General Availability, while breaking changes are still possible. These runtimes and images may be modified or discontinued without notice.
Is there a chance that images without -preview were already pushed to the registry around July 8th?
I have seen a dependency update bot update a Dockerfile to use FROM public.ecr.aws/lambda/python:3.15 and that image seems to have disappeared again.
The image disappearing would match the fact that 3.15 is not officially out yet. Can you help explain how it existed for a timeframe between July 8th and July 22nd?
Besides being built, the image has not run yet, so I can't provide actual feedback.
Thanks @erpel for reaching out! You're right, during our build/testing process we did incorrectly push non-preview 3.15 tags to public.ecr.aws/lambda/python, which is why FROM public.ecr.aws/lambda/python:3.15 resolved for a while and then went away.
That tag shouldn't have been published yet, and we're sorry for the inconvenience this caused with your dependency update bot.
For now, please keep using public.ecr.aws/lambda/python:3.15-preview (still experimental, not for production use). We will eventually publish the 3.15 tags once the runtime is no longer in preview.
Activity
erpel commentedon Aug 4, 2026
Is there a chance that images without -preview were already pushed to the registry around July 8th?
I have seen a dependency update bot update a Dockerfile to use
FROM public.ecr.aws/lambda/python:3.15and that image seems to have disappeared again.The image disappearing would match the fact that 3.15 is not officially out yet. Can you help explain how it existed for a timeframe between July 8th and July 22nd?
Besides being built, the image has not run yet, so I can't provide actual feedback.
maxday commentedon Aug 4, 2026
Thanks @erpel for reaching out! You're right, during our build/testing process we did incorrectly push non-preview
3.15tags topublic.ecr.aws/lambda/python, which is whyFROM public.ecr.aws/lambda/python:3.15resolved for a while and then went away.That tag shouldn't have been published yet, and we're sorry for the inconvenience this caused with your dependency update bot.
For now, please keep using
public.ecr.aws/lambda/python:3.15-preview(still experimental, not for production use). We will eventually publish the3.15tags once the runtime is no longer in preview.