AWS

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.

Secrets are usually retrieved far more often than they are changed. The AWS Secrets Manager cache lets you cache secrets for a specified period, reducing the number of requests your applications need to make.

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.