Secrets Manager

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.

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.

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.

When a Lambda function is connected to a VPC, accessing the Secrets Manager becomes more complicated because the function no longer has internet access. One way to resolve this is to use a VPC endpoint.

In an earlier post I showed how to use a .NET 6 Lambda function to retrieve a secret from Secrets Manager synchronously, but it is also easy to do this asynchronously.

.NET Lambda functions can get secrets from AWS Secrets Manager, but you need to grant the Lambda function permission to access the secret. Read on to find out how.