AWS Lambda

The release of .NET 7 brings with it a new way to compile and run .NET code - native AOT compilation. This post compares the cold start time of a Lambda function running on .NET 7 after native AOT compilation with the cold start time of a Lambda function running on .NET 6 with the managed runtime. The results are surprisingly good.

Cold starts with .NET AWS Lambda functions are a concern for some, but provisioned concurrency provides a simple and cost-effective way to keep your Lambda function warm.

There may be times when you want to share information between Lambda functions, using a distributed memory cache will help you do this.

Lambda layers allow you to leverage functionality provided by AWS. This post shows how to use the AWS Parameters and Secrets Lambda Extension to cache Secrets Manager secrets.

In part two of this series you will see how to perform constructor and method dependency injection on simple AWS Lambda functions (deployed with dotnet lambda deploy-function) using the new Amazon.Lambda.Annotations library.

In part one of this series you will see how to perform constructor and method dependency injection on AWS Lambda applications (deployed with dotnet lambda deploy-serverless) using the new Amazon.Lambda.Annotations library.

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.