AWS Lambda

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.

When a Lambda function is connected to a VPC, the function can no longer access the internet. One way to resolve this is to use a NAT gateway, read on to see how.

This post shows how easy it is to create a simple Lambda function written in C#.

In a previous post, I showed how to use a VPC Endpoint to give a Lambda function (which is connected to the VPC) access to Secrets Manager. In this post, I will show how to use a NAT Gateway to give a Lambda function access to Secrets Manager and the internet.

Calling one Lambda function from another is something you’ll occasionally need to do. If you are using Lambda function URLs it is a simple HTTP request. But you can also use the AWS Lambda SDK to invoke the other function.