Skip to main content

NAT Gateway


NAT Gateway

Create a VPC with two subnets and allow public access to EC2 instances only on one subnet. Then enable the internet to EC2 instances in Private Subnet.



Requirement:

Create EC2 instance in private Subnet and provide Internet access using NAT Gateway.

Solution:

1.       Create One VPC with CIDR Range 10.0.0.0/16
2.       Create a private Subnet with CIDR Range 10.0.1.0/24
3.       Create a public Subnet with CIDR Range 10.0.2.0/24
4.       Create One Internet Gateway and assign to VPC.
5.       Create one custom Route table and associate Public Subnet.
a.       Create a global route (0.0.0.0/0) and target to IGW
6.       Associate private subnet to default Route table
7.       Launch one EC2 instance (VM1) in public Subnet with Public IP enabled.
8.       Launch another EC2 instance (VM2) in private Subnet with only Private IP.
9.       Navigate to VPC à Nat Gateways
10.   Click on Create NAT Gateway button
11.   In Subnet dropdown select Public Subnet
12.   Click on Create New IP button for allocating Elastic IP Allocation ID the click on Create a NAT Gateway button.
13.       Navigate to Route tables à Default Route table à Routes à Edit Routes
14.       Add Global routes (0.0.0.0/0) and select Nat Gateway from the Target drop-down and select the NAT Gateway ID then click on Save routes button.
15.       Login to VM1 instance with Public IP and SSH to VM2 using private IP and test the internet.
Note: You must copy the pem file used for VM2 instance and change the permission to 400

chmod 400 <pem file>
ssh -i <pem file> ec2-user@<private IP of EC2>

[ec2-user@ip-10-0-1-211 ~]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=50 time=3.22 ms
Labels:

Comments

Post a Comment

Popular posts from this blog

VPC Peering

VPC Peering VPC Peering feature is used when we need to establish connectivity between subnet in two different VPCs in the same or different account. Let’s take a scenario of creating VPC Peering between two VPC in the same account to keep it simple. NOTE: All the IP address and CIDR range depicted in the below diagram and subsequent steps is for example only. Step 1: Create a VPC A with CIDR Range 10.0.0.0/16 and keep Default in Tenancy dropdown.   Step 2: Create a VPC B with CIDR Range 172.16.0.0/16 and keep Default in Tenancy dropdown.  Step 3: Enter Name tag as SubNetA and map to VPC A in VPC dropdown. Note that VPC CIDRs of VPC A is auto-populated and status as associated. Selecting Availability zone is not mandatory. However, AWS will select one of the Availability Zone when we create a subnet. Enter 10.0.1.0/24 as IPv4 CIDR block and then click on Create button. Step 4: Create SubNet A and map to VPC B in VPC dropdown. Note that CIDR o
Post a Comment
Read more

IP Sec Tunneling

Requirement: Establish connectivity between the on-premise data center and AWS data center using IPSec tunneling.  Solution: We are creating IPSec Tunneling between two VPC in a different account and the different region as we don’t have on-premise data center.  Steps to achieve this. 1.        Create VPC A with CIDR Range 10.100.0.0/16 in First account. 2.        Create Subnet A in VPC A with range 10.100.1.0/24 3.        Create Internet Gateway and attach to VPC A. 4.        Add the Route (0.0.0.0/0) in default Route Table and target to Internet Gateway. 5.        Create VPC B with CIDR Range 10.200.0.0/16 in Second account. 6.        Create Subnet B in VPC B with range 10.200.1.0/24 7.        Create Internet Gateway and attach to VPC B. 8.        Add the Route (0.0.0.0/0) in default Route Table and target to Internet Gateway. 9.        Below steps to be executed at VPC B a.        Launch the EC2 instance in VPC B with Public IP enabled.
Post a Comment
Read more