The lambda runtime used for the functions is python3.7. This runtime is being deprecated on lambda on Nov 27, 2023 (Phase 1).
Are there plans to upgrade and test using a newer runtime before AWS stop supporting the current runtime?
A reproducible test case or series of steps
Nothing out of the ordinary here.
The version of our code being used
5.18
Any modifications you've made relevant to the bug
No
Anything unusual about your environment or deployment
No. Deployed using SAM cli.
Following is the notice from AWS regarding the deprecation:
We are ending support for Python 3.7 in AWS Lambda. This follows Python 3.7 End-Of-Life (EOL) reached on June 27, 2023 [1].
As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 27, 2023, Lambda will no longer apply security patches and other updates to the Python 3.7 runtime used by Lambda functions, and functions using Python 3.7 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Python 3.7 runtime. Starting January 25, 2024, you will no longer be able to update existing functions using the Python 3.7 runtime.
We recommend that you upgrade your existing Python 3.7 functions to Python 3.11 before November 27, 2023.
Upgrade deprecated python runtime
The lambda runtime used for the functions is
python3.7
. This runtime is being deprecated on lambda on Nov 27, 2023 (Phase 1).Are there plans to upgrade and test using a newer runtime before AWS stop supporting the current runtime?
A reproducible test case or series of steps
The version of our code being used
Any modifications you've made relevant to the bug
Anything unusual about your environment or deployment
Following is the notice from AWS regarding the deprecation: