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.

No Dogma Blog (Bryan Hogan)

A step-by-step guide for giving a .NET Lambda function (connected to a VPC) access to AWS Secrets Manager via a NAT Gateway. Covers allocating an Elastic IP, creating the NAT Gateway on a public subnet, setting up a new route table, associating the private subnet, and adding a route directing internet traffic through the NAT Gateway — restoring Secrets Manager access without using a VPC Endpoint.

Accessing AWS Secrets Manager from .NET Lambda Functions, Part 4 - Connected to a VPC, and using a NAT Gateway

Why connect a Lambda function to the VPC?