.NET 8 reached end of support on November 10, 2026, and AWS deprecated the dotnet8 Lambda runtime the same day. Your functions still run, but AWS no longer patches the runtime or supports them. Updates are blocked from August 31, 2027.
| Runtime | Deprecated | Creating functions blocked | Updating functions blocked |
|---|---|---|---|
dotnet8 | November 10, 2026 | July 29, 2027 | August 31, 2027 |
dotnet6 | December 20, 2024 | July 29, 2027 | August 31, 2027 |
dotnet10 (the replacement) | November 14, 2028 | December 14, 2028 | January 15, 2029 |
The .NET 9 container base image was deprecated on November 10, 2026 too.
dotnet8 functions; the AWS CLI, AWS SAM and CloudFormation still do until the block dates.dotnet8. Use versions and aliases so you can roll back to a tested version instead.aws lambda list-functions --function-version ALL --region us-east-1 \
--output text --query "Functions[?Runtime=='dotnet8'].FunctionArn"
Repeat it for every region and every account, and again with dotnet6. AWS Trusted Advisor's "AWS Lambda Functions Using Deprecated Runtimes" check lists them too, but only on support plans with the full set of Trusted Advisor checks, such as Business Support+ and Enterprise Support; Basic and Developer Support plans don't include it. Functions deployed as container images don't show a runtime here: look for images built from the .NET 8 or .NET 9 Lambda base images.
<TargetFramework>net10.0</TargetFramework> and update the Amazon.Lambda.* and AWS SDK packages to current versions.dotnet10 in your SAM, CDK, Terraform or CloudFormation templates. For container images, rebuild from the .NET 10 Lambda base image.Functions where cold starts matter can also be compiled with Native AOT, which runs on the same managed dotnet10 runtime (or on the OS-only provided.al2023 runtime); that's a bigger change, so do it after the runtime upgrade, not with it.