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
SAM CLI will stop supporting .NET Core 3.1 by May 3rd, 2023.
This runtime is no longer supported by AWS Lambda, and it is on the deprecation path. Users are not able to deploy/update these functions anymore.
What is deprecation schedule?
After May 3rd 2023, SAM CLI will no longer allow customers to use deprecated runtimes within the CLI.
Am I impacted by this deprecation?
You are impacted by this if you are still using the .NET Core 3.1 runtime. The recommendation is to upgrade these runtimes to a newer version which is supported by AWS Lambda.
Lambda already finished the phase 2 deprecation for .Net Core 3.1 on May 3, 2023 (Get more info about lambda runtimes deprecation policy here). SAM CLI also deprecated supporting .Net Core 3.1 in the latest release 1.89.0
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
SAM CLI will stop supporting .NET Core 3.1 by May 3rd, 2023.
This runtime is no longer supported by AWS Lambda, and it is on the deprecation path. Users are not able to deploy/update these functions anymore.
What is deprecation schedule?
After May 3rd 2023, SAM CLI will no longer allow customers to use deprecated runtimes within the CLI.
Am I impacted by this deprecation?
You are impacted by this if you are still using the .NET Core 3.1 runtime. The recommendation is to upgrade these runtimes to a newer version which is supported by AWS Lambda.
For more information about supported runtimes by AWS Lambda, please check https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html
AWS Lambda Builders will stop support using it as a library for .NET Core 3.1, see aws/aws-lambda-builders#479 for more details.
The text was updated successfully, but these errors were encountered: