BestPaid guides · AWS · .NET

AWS Lambda deprecated the dotnet8 runtime on November 10, 2026. Here is how to move your functions to .NET 10

.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.

Sources: AWS's Lambda runtimes and runtime deprecation pages, and the Trusted Advisor check reference. Checked on November 21, 2026; AWS says its dates are subject to change. This page is our own summary; follow AWS's documentation for every detail.

The dates

RuntimeDeprecatedCreating functions blockedUpdating functions blocked
dotnet8November 10, 2026July 29, 2027August 31, 2027
dotnet6December 20, 2024July 29, 2027August 31, 2027
dotnet10 (the replacement)November 14, 2028December 14, 2028January 15, 2029

The .NET 9 container base image was deprecated on November 10, 2026 too.

What "deprecated" means for a running function

1. Find every .NET 8 function

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.

2. Move each function to dotnet10

  1. Set <TargetFramework>net10.0</TargetFramework> and update the Amazon.Lambda.* and AWS SDK packages to current versions.
  2. Change the runtime to dotnet10 in your SAM, CDK, Terraform or CloudFormation templates. For container images, rebuild from the .NET 10 Lambda base image.
  3. Work through the .NET 9 and .NET 10 breaking changes that touch your code. Our .NET 8 to .NET 10 checklist lists the usual ones.
  4. Publish a new version, point a test alias at it, compare logs, duration and errors, then move the production alias.

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.

Dozens of .NET functions across accounts? We move .NET 6 and .NET 8 Lambda functions to .NET 10 at a fixed price, together with the rest of your .NET estate if you like. It starts with a $490 audit: every function, its packages and its breaking changes, with a fixed quote.
See the .NET upgrade offer
Still on AWSSDK V3 packages? The AWS SDK for .NET V3 reached end of support on June 1, 2026: how to move to V4.