AWS Lambda

The mediator pattern is very helpful for keeping business logic out of your API endpoints. This post provides a simple example of this with the MediatR library.

Setting up dependency injection for your .NET Lambda functions only takes a few lines of code. Read on to see how.

If you are Amazon.Lambda.Templates, version 6.3.0 or earlier with .NET 7 RC 1, you may get an error when creating new project templates. Read on for a fix or a workaround.

It is to use environment variables in your .NET Lambda functions, and they are quick to update. Read on to see how.

With Lambda versions and aliases you can setup A/B testing for your functions. This example uses .NET 6 and Lambda Function URLs, but the same principles apply to other languages.

This is a simple Lambda function that uses a Function URL. This blog post will be referenced in more complicated examples.

If you want to experiment with code variations for a Lambda function, try Lambda versions. In this post, you’ll see how to deploy a stable and experimental version of the same function.

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

If you are using IAM auth with Lambda Function URLs, and you want to call the function using HttpClient from a .NET application, you need to sign the request. Read on to see how.

Even though Lambda functions are “serverless”, and even though there is no guarantee how long a function will remain “warm” for, you might still get good use out of a memory cache.