how-to-setup-lambda-to-talk-to-internet-and-vpc.md

How to setup AWS lambda function to talk to the internet and VPC

I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.

So it might be really unintuitive at first but lambda functions have three states.

1. No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
2. VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
3. VPC with NAT, The best of both worlds, AWS services and web.

I'm gonna walk you through the steps to set up number 3.

Note: This tutorial isn't exactly in order of steps, you may need to create one thing (subnet, nat, route table) then go back into the settings for something previously created and edit it to use a newly thing.

Creating Subnets

VPC Dashboard > Subnets

This is what I had to start with, my existing vpc that I wanted to connect to already had 4 subnets. Here I noticed I had a couple of subnets already set up. Below is a totally fake ip I pulled from the internet. But the patten of increments of 16 is recreated here.

Note: DO NOT use 131.179.0.0/16 it's just an example.

VPC	CIDR
vpc-████████ (131.179.0.0/16)	131.179.0.0/20
vpc-████████ (131.179.0.0/16)	131.179.16.0/20
vpc-████████ (131.179.0.0/16)	131.179.32.0/20
vpc-████████ (131.179.0.0/16)	131.179.48.0/20

Here I created three four new subnets.

VPC	CIDR	name
vpc-████████ (131.179.0.0/16)	131.179.64.0/20	lambda-subnet-point-to-nat-1
vpc-████████ (131.179.0.0/16)	131.179.80.0/20	lambda-subnet-point-to-nat-2
vpc-████████ (131.179.0.0/16)	131.179.96.0/20	lambda-subnet-point-to-nat-3
vpc-████████ (131.179.0.0/16)	131.179.112.0/20	lambda-subnet-point-to-igw

Note: Here igw stands for Internet Gateway and nat stands for network address translation gateway (NAT Gateway).

Three of them will point to the nat and one points to the igw.

Let's create the Route Tables now.

Creating Route Tables

VPC Dashboard > Route Tables

Your going to want to set up two Route Tables.

One that points to your nat let's call this lambda-rt-to-nat:

Destination	Target
131.179.0.0/16	local
0.0.0.0/0	nat-█████████████████

One that points to your igw let's call this lambda-rt-to-igw:

Destination	Target
131.179.0.0/16	local
0.0.0.0/0	igw-████████

Your gonna want to go into each of the subnet and assign them to their corresponding route table.

subnet name	route table name
lambda-subnet-point-to-nat-1	lambda-rt-to-nat
lambda-subnet-point-to-nat-2	lambda-rt-to-nat
lambda-subnet-point-to-nat-3	lambda-rt-to-nat
lambda-subnet-point-to-igw	lambda-rt-to-igw

Set your lambda up

Lambda > Functions > my-function > Configuration > Advanced Settings

Now you want to set up your lambda function to use the subnets you created.

Setup your lambda to use your VPC.

VPC

vpc-████████ (131.179.0.0/16)

Here you setup lambda to use the subnets that point directly to your nat.

Subnets*

subnet name
lambda-subnet-point-to-nat-1
lambda-subnet-point-to-nat-2
lambda-subnet-point-to-nat-3

Create a NAT

VPC Dashboard > NAT Gateways > Create NAT Gateway

Your going to want click Create NAT Gateway and set the Subnet* to lambda-subnet-point-to-igw, and Create New EIP.

Fin

That should be it! Your lambda should be able to talk to both the VPS and the web through a NAT! Comment below if you need help or want to clarify anything here!

Links

• Essentials: Introducing VPC Support for AWS Lambda
• AWS Lambda: How to setup a NAT gateway for a lambda function with VPC access
• New – Access Resources in a VPC from Your Lambda Functions
• Configuring a Lambda Function to Access Resources in an Amazon VPC
• February 2016 Webinar Series - Introducing VPC Support for AWS Lambda

Shameless SEO terms

• amazon lambda nat
• aws lambda vpc web
• aws lambda rds and web
• aws lambda rds and http request
• lambda timeout
• AWS lambda timeout random vpc

is there something on how to setup this using an vpc endpoint instead of a NAT gateway?

rel: https://stackoverflow.com/a/52994841/6323666

This saved me quite a lot of struggling - eternally grateful for the article, 10/10!

Thank you! Works for me!!!

Thanks! This works for me too 👍

And how the fuck I must to solve the issue with boto3 hangs up in lambda without this....
Nice!

Advice: Create new VPC for Lambda! Don't use your current production one, if you don't understand what is 'route tables', igw, nat or you under the risk to stop the show.

Holy crap what a mess, but it works. Just be very careful to follow the pattern for the CIDR values in the new subnets you will create. I had to inspect my existing subnets and pick up where they left off, incrementing the CIDR by 16 for each. So I wound up creating subnets with CIDR values of:

131.179.96.0/20
131.179.112.0/20
131.179.128.0/20
131.179.144.0/20

AND please be careful to note that the 131.179 portion is dummy data - you have to look at your existing subnets and get your values there.

Lastly... I tested connectivity to my RDS instance as I went through the steps. It was when I applied the new subnets to the Lambdas' VPC that they lost connectivity to RDS. So I added my previous subnets back in, and then each Lambda has 5 subnets in it's VPC assignment - three that go through to the nat and two that go to RDS. This allowed my Lambdas to hit both networks.

Thanks this helped a lot. I set it up and it worked, but then after a while I am back as before... Lambda timing out. Are there any additional configurations to be made to the NAT or subnets so that they don't sleep or something? Also, why 3 subnets pointing to NAT?

Check out a new feature on Lambda called SnapStart. That might fix the timeouts.
I haven't tried it though.

At the point where you say: 'One that points to your nat let's call this lambda-rt-to-nat' I don't have any NAT's to choose from. Should I create one first at this point? Could you provide me with the correct settings for it?

@RickGroenewegen Hey Rick, I'm sorry I can't answer your question I haven't really been using AWS much lately.

You are my hero, thank you!!

This was very helpful. Thank you

didnt work. still timeouts

Thank you very much great article !