AWS Lambda

It’s easy to run a .NET 6 Web API application on Lambda using the custom runtime option, this post explains how, and gives the CLI commands to have it up and running in a few minutes.

With the AWS tools and templates for Lambdas it is very easy to build and deploy a .NET 6 Web API application as a container image.

A couple of new features in .NET 6 improve Lambda cold start times and the speed of deploying new functions. Read on to see how.

Want to run a .NET 6 Lambda on ARM64?

You can’t yet run .NET 6 on AWS Lambda with the familiar managed runtime, but you can with a custom runtime. Here are the few small steps you need.

Calling an AWS Lambda from Windows 10 is different depending on the shell you are using. In this post, I’ll show how to call a simple Lambda that takes a simple event document from PowerShell, the command prompt, the WSL Ubuntu shell, and the git bash shell.

I’ve been working on a small AWS Lambda that has needed many iterations, I quickly got tired of building it, zipping by hand from Windows UI, uploading from the AWS console UI, and executing a test from there. Here is a simple batch file that does it all.

AWS Step Functions are a very easy way to orchestrate many things. But they can also be used to run a Lambda at an exact time (down to a tenth of a second, or less), up to a year in the future.

After playing with .NET 5 libraries and Web API applications inside Lambda containers I wanted to see if I could get a .NET 6 library running too….I did, read on.

In my previous post I showed how to build a .NET 5 library inside a docker image and deploy it to an AWS Lambda. This post is a small extension on that. I’m going to build a .NET 5 Web API application, turn it into a docker image, deploy it to an AWS Lambda, and connect an API Gateway to the Lambda to call the controller inside the application, inside the container, inside the Lambda!