timetobail

AWS Lambda · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on Lambda functions on .NET 8?

Time to Bail · Boarding pass

FromLambda functions on .NET 8
ToYour pick

Act. You can stay.

.NET 8 on Lambda is deprecated November 10, 2026. Updates to these functions are blocked from August 31, 2027.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Deprecation date
Time left
23days
Status
Act

AWS Lambda .NET 8 runtime deprecated November 10, 2026

AWS deprecates the .NET 8 runtime (dotnet8) for Lambda on November 10, 2026. After that it may get no more security patches. Creating functions is blocked from July 29, 2027, and updating them from August 31, 2027.

Email me 7 days before Nov 10

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

How it is winding down

  1. Nov 10, 2026Deprecation dateNext
  2. Jul 29Creating new functions blocked
  3. Aug 31Updating functions blocked

What to do before November 10

Tick steps as you go. Your progress stays in this browser.

  1. Find functions on .NET 8

    Filter by runtime in the Lambda console, or list dotnet8 functions with the AWS CLI in each region.

  2. Move to .NET 10

    Build the project for .NET 10 and set the runtime to dotnet10. Update NuGet packages.

  3. Test and deploy before the blocks

    Test each function on the new runtime. After August 31, 2027 you cannot update a dotnet8 function.

Email me 7 days before Nov 10

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
Deprecation dateNovember 10, 2026[1]
Runtimedotnet8 (.NET 8 on Amazon Linux 2023)[1]
Creating new functions blockedJuly 29, 2027[1]
Updating functions blockedAugust 31, 2027[1]
Container-only .NET runtime.NET 9 (container image only) is also deprecated November 10, 2026; block dates not scheduled[1]
After deprecationAWS may stop security patches and technical support; you can still invoke your functions[1]
In the Lambda consoleFrom the deprecation date you cannot create or update these functions there; the AWS CLI, AWS SAM and CloudFormation still work until the blocks[1]
Once updates are blockedYou cannot go back to the deprecated runtime[1]
How AWS tells youEmail and Health Dashboard notices at least 180 days before; Trusted Advisor lists the functions[1]
Can the dates change?Yes. AWS says the dates are for planning and subject to change[1]
How to list themaws lambda list-functions --function-version ALL --region us-east-1 --query "Functions[?Runtime=='dotnet8'].FunctionArn" (once per region)[2]
Newer .NET runtimesdotnet10 (.NET 10) until November 14, 2028[1]
Functions on .NET 8May get no security patches after November 10, 2026; no updates from August 31, 2027[1]

After November 10, 2026 you will see

In the Lambda console you can no longer create or update functions on dotnet8. The AWS CLI, AWS SAM and CloudFormation still work until the blocks. Your functions keep running, but AWS may stop security patches.

Fix

  1. Find your dotnet8 functions: aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='dotnet8'].FunctionArn". Run it in each region.
  2. Change the runtime to dotnet10. Test it before you ship.
  3. Use versions and aliases, so you can roll back.
  4. Finish before July 29, 2027 (no new functions) and August 31, 2027 (no updates).

Source: [1] Lambda runtimes (Amazon Web Services) · [2] Retrieve data about Lambda Event Functions that use a deprecated runtime (Amazon Web Services)

Sources

Check it yourself. Every fact above links here.

  1. Lambda runtimes Amazon Web Services · primary · checked Oct 17
  2. Retrieve data about Lambda Event Functions that use a deprecated runtime Amazon Web Services · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on Lambda functions on .NET 8? Act. You can stay. .NET 8 on Lambda is deprecated November 10, 2026. Updates to these functions are blocked from August 31, 2027.

On our scale this is Act: change a setting or plan before the date. You can stay.

AWS deprecates the .NET 8 runtime (dotnet8) for Lambda on November 10, 2026. After that it may get no more security patches. Creating functions is blocked from July 29, 2027, and updating them from August 31, 2027.

Here are the facts we checked:

  • Deprecation date: November 10, 2026 (Amazon Web Services)
  • Runtime: dotnet8 (.NET 8 on Amazon Linux 2023) (Amazon Web Services)
  • Creating new functions blocked: July 29, 2027 (Amazon Web Services)
  • Updating functions blocked: August 31, 2027 (Amazon Web Services)
  • Container-only .NET runtime: .NET 9 (container image only) is also deprecated November 10, 2026; block dates not scheduled (Amazon Web Services)
  • After deprecation: AWS may stop security patches and technical support; you can still invoke your functions (Amazon Web Services)
  • In the Lambda console: From the deprecation date you cannot create or update these functions there; the AWS CLI, AWS SAM and CloudFormation still work until the blocks (Amazon Web Services)
  • Once updates are blocked: You cannot go back to the deprecated runtime (Amazon Web Services)
  • How AWS tells you: Email and Health Dashboard notices at least 180 days before; Trusted Advisor lists the functions (Amazon Web Services)
  • Can the dates change?: Yes. AWS says the dates are for planning and subject to change (Amazon Web Services)
  • How to list them: aws lambda list-functions --function-version ALL --region us-east-1 --query "Functions[?Runtime=='dotnet8'].FunctionArn" (once per region) (Amazon Web Services)
  • Newer .NET runtimes: dotnet10 (.NET 10) until November 14, 2028 (Amazon Web Services)
  • Functions on .NET 8: May get no security patches after November 10, 2026; no updates from August 31, 2027 (Amazon Web Services)

You can stay on AWS Lambda. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Amazon Web Services is the main source for this page. AWS Lambda has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Functions on .NET 8: May get no security patches after November 10, 2026; no updates from August 31, 2027.

The date to remember is November 10, 2026. Make the change before then.

What to do before November 10

  1. Find functions on .NET 8. Filter by runtime in the Lambda console, or list dotnet8 functions with the AWS CLI in each region.
  2. Move to .NET 10. Build the project for .NET 10 and set the runtime to dotnet10. Update NuGet packages.
  3. Test and deploy before the blocks. Test each function on the new runtime. After August 31, 2027 you cannot update a dotnet8 function.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Lambda functions on .NET 8 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.