mervintankw · December 21, 2021 23:46 · Jun 13, 2016 · Jun 13, 2016 · Jun 13, 2016 · Jun 13, 2016
diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -2,7 +2,7 @@
 
 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 tbe really unintuitive but lambda functions have three states.
+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.

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -10,6 +10,8 @@ So it might tbe really unintuitive but lambda functions have three states.
 
 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

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -117,3 +117,5 @@ That should be it! Your lambda should be able to talk to both the VPS and the we
 * aws lambda vpc web
 * aws lambda rds and web
 * aws lambda rds and http request
+* lambda timeout 
+* AWS lambda timeout random vpc
diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -92,6 +92,12 @@ 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!

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -16,7 +16,7 @@ I'm gonna walk you through the steps to set up number `3`.
 
 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` as your number use your vpc local ip and substitute the pattern.
+> Note: DO NOT use `131.179.0.0/16` it's just an example.
 
 VPC|CIDR
 --- | ---

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -94,7 +94,7 @@ lambda-subnet-point-to-nat-3 |
 
 ## Fin
 
-That should be it! Your lambda should be able to talk to both the VPS and the web through a NAT!
+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
 

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -102,8 +102,10 @@ That should be it! Your lambda should be able to talk to both the VPS and the we
 * [AWS Lambda: How to setup a NAT gateway for a lambda function with VPC access](http://stackoverflow.com/questions/35455281/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](https://aws.amazon.com/blogs/aws/new-access-resources-in-a-vpc-from-your-lambda-functions/)
 * [Configuring a Lambda Function to Access Resources in an Amazon VPC](http://docs.aws.amazon.com/lambda/latest/dg/vpc.html)
+* [February 2016 Webinar Series - Introducing VPC Support for AWS Lambda](https://www.youtube.com/watch?v=Qn8uGcfBb_I)
 
-## For SEO
+
+## Shameless SEO terms
 
 * amazon lambda nat
 * aws lambda vpc web

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -90,4 +90,22 @@ subnet name |
 --- |
 lambda-subnet-point-to-nat-1 |
 lambda-subnet-point-to-nat-2 |
-lambda-subnet-point-to-nat-3 |
+lambda-subnet-point-to-nat-3 |
+
+## Fin
+
+That should be it! Your lambda should be able to talk to both the VPS and the web through a NAT!
+
+## Links
+
+* [Essentials: Introducing VPC Support for AWS Lambda](http://www.slideshare.net/AmazonWebServices/february-2016-webinar-series-accessing-resources-in-vpc-with-aws-lambda)
+* [AWS Lambda: How to setup a NAT gateway for a lambda function with VPC access](http://stackoverflow.com/questions/35455281/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](https://aws.amazon.com/blogs/aws/new-access-resources-in-a-vpc-from-your-lambda-functions/)
+* [Configuring a Lambda Function to Access Resources in an Amazon VPC](http://docs.aws.amazon.com/lambda/latest/dg/vpc.html)
+
+## For SEO
+
+* amazon lambda nat
+* aws lambda vpc web
+* aws lambda rds and web
+* aws lambda rds and http request
diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -86,8 +86,8 @@ 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
+subnet name |
+--- |
+lambda-subnet-point-to-nat-1 |
+lambda-subnet-point-to-nat-2 |
+lambda-subnet-point-to-nat-3 |
diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -68,4 +68,26 @@ 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
+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
diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -8,7 +8,7 @@ So it might tbe really unintuitive but lambda functions have three states.
 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.
 
-This is where your gonna edit the setting for the lambda to enable VPC and set the subnets.
+I'm gonna walk you through the steps to set up number `3`.
 
 ## Creating Subnets
 
@@ -38,6 +38,8 @@ vpc-████████ (131.179.0.0/16)|131.179.112.0/20|lambda-subnet-poi
 
 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
@@ -58,7 +60,8 @@ Destination|Target
 131.179.0.0/16 | local 
 0.0.0.0/0 | igw-████████
 
-Now connect all of the `subnets` to the corresponding `route table`.
+
+Your gonna want to go into each of the subnet and assign them to their corresponding `route table`.
 
 subnet name | route table name
 ---|---

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -14,7 +14,7 @@ This is where your gonna edit the setting for the lambda to enable VPC and set t
 
 > VPC Dashboard > 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.
+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` as your number use your vpc local ip and substitute the pattern.
 
@@ -25,7 +25,7 @@ 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.
+Here I created three four new `subnets`.
 
 VPC|CIDR|name
 --- | --- | ---

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -56,4 +56,13 @@ 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-████████
+0.0.0.0/0 | igw-████████
+
+Now connect all of the `subnets` to the 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
diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -10,6 +10,8 @@ So it might tbe really unintuitive but lambda functions have three states.
 
 This is where your gonna edit the setting for the lambda to enable VPC and set the subnets.
 
+## Creating Subnets
+
 > VPC Dashboard > 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.
@@ -34,7 +36,11 @@ vpc-████████ (131.179.0.0/16)|131.179.112.0/20|lambda-subnet-poi
 
 > 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`.
+Three of them will point to the `nat` and one points to the `igw`.
+
+## Creating Route Tables
+
+> VPC Dashboard > Route Tables
 
 Your going to want to set up two `Route Tables`.
 

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -36,16 +36,16 @@ vpc-████████ (131.179.0.0/16)|131.179.112.0/20|lambda-subnet-poi
 
 Three of them will point to the nat and one points to the `igw`.
 
-Your going to want to set up two routing tables
+Your going to want to set up two `Route Tables`.
 
-One that points to your `nat`:
+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`:
+One that points to your `igw` let's call this `lambda-rt-to-igw`:
 
 Destination|Target
 ---|---

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -26,6 +26,7 @@ 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

diff --git a/how-to-setup-lambda-to-talk-to-internet-and-vpc.md b/how-to-setup-lambda-to-talk-to-internet-and-vpc.md
@@ -0,0 +1,52 @@
+# 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 tbe really unintuitive 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.
+
+This is where your gonna edit the setting for the lambda to enable VPC and set the subnets.
+
+> VPC Dashboard > 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` as your number use your vpc local ip and substitute the pattern.
+
+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`.
+
+Your going to want to set up two routing tables
+
+One that points to your `nat`:
+
+Destination|Target
+---|---
+131.179.0.0/16 | local 
+0.0.0.0/0 | nat-█████████████████
+
+One that points to your `igw`:
+
+Destination|Target
+---|---
+131.179.0.0/16 | local 
+0.0.0.0/0 | igw-████████
No results found