News

Amazon Cloud Broadens .NET Core Choices for AWS Lambda Functions

Microsoft-centric developers working with the Amazon cloud platform now have more .NET Core choices to handle their AWS Lambda functions for serverless, event-driven programming.

Amazon Web Services (AWS) this week released a new Amazon.Lambda.RuntimeSupport library to support the use of more .NET Core runtime options.

Previously, developers could only use Long Term Support (LTS) versions of .NET Core to handle AWS Lambda functions. LTS versions are supported by Microsoft for either three years after an initial release or for one year after a subsequent LTS version is released, whichever is longer.

After LTS, Microsoft has a Current release support designation, providing support for three months after a subsequent Current or LTS release.

And finally, Microsoft supports Preview releases if they carry a "Go-Live" designation, meaning they can be used in production.

Prior to the new support library, developers could only use LTS .NET Core versions built into the AWS Lambda service, of which the latest is .NET Core 2.1. Going forward, AWS Lambda will continue to build-in only LTS versions of .NET Core. However, coders can use the new support library to create Lambda functions using Current and Preview versions of .NET Core that are compatible with .NET Standard 2.0, which provides a specification representing a set of APIs that all .NET platforms must implement.

"If you're looking to use new features from .NET Core 2.2 or 3.0 preview, Amazon.Lambda.RuntimeSupport gives you a path forward," AWS said in a post.

That path may prove to be a bit more complicated, however, as programmers using those other .NET Core versions must create custom runtimes to leverage non-supported languages or runtimes.

While AWS will automatically apply periodic security updates and bug fixes to its built-in .NET Core runtimes, the company said: "The customer manages updates to custom runtimes, but has flexibility to bring any version of a runtime to the platform. Keep this in mind when choosing between a built-in runtime and a custom runtime."

AWS has been steadily increasing its .NET Core support, having introduced .NET Core 2.1 support for AWS Lambda in July of last year and integrating AWS Lambda with PowerShell Core 6.0 a couple months later.

Source code for the new library is available on GitHub, and it also comes in a NuGet package.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Microsoft Highlights Visual Studio Live! Event Lineup and Longtime Developer Community Role

    A Microsoft MVP Blog post on Visual Studio Live!'s longevity arrives as the 2026 conference series continues with upcoming stops at Microsoft HQ, San Diego and Orlando.

  • Using Local AI to Cut Copilot Usage-Based Billing Shock

    After being gobsmacked by the new billing plan using almost all my monthly credits in one or two days, I tried pushing some Copilot-style coding work onto local models in VS Code. What I found was less "free AI" and more "pick your pain": cloud charges on one side, heavy local resource use and long waits on the other.

  • .NET 11 Preview 5 Focuses on Performance, Productivity and Safer Code

    .NET 11 Preview 5 focuses on under-the-hood runtime performance gains, streamlined APIs and language features that reduce boilerplate, plus built‑in security checks and incremental ASP.NET Core and EF Core improvements aimed at everyday developer productivity.

  • VS Code 1.124 Focuses on Agent Autonomy and Parallel Sessions

    Microsoft's June 2026 VS Code update turns on Autopilot by default and adds background sending for agent sessions.

Subscribe on YouTube