{"id":12664,"date":"2014-04-03T13:51:30","date_gmt":"2014-04-03T08:21:30","guid":{"rendered":"https:\/\/2thenew.xyz\/blog\/?p=12664"},"modified":"2014-04-15T16:12:15","modified_gmt":"2014-04-15T10:42:15","slug":"vpc-explained-part-2-vpc-with-public-and-private-subnets","status":"publish","type":"post","link":"https:\/\/2thenew.xyz\/blog\/vpc-explained-part-2-vpc-with-public-and-private-subnets\/","title":{"rendered":"VPC Explained Part-2 : VPC with Public and Private subnets."},"content":{"rendered":"

<\/a>In my last blog we saw how a VPC with single public subnet is implemented. And now in this blog we will go through the second scenario of aws VPC i.e. a VPC with public and private subnets.<\/p>\n

Let’s create a VPC with two subnets , Public and Private.<\/p>\n

1.<\/p>\n

Login to your Amazon account and click on VPC in the services drop down to move on VPC Dashboard. Now you can choose a specific region (Singapore here) as per your choice.<\/p>\n

Click on \u201cStart VPC Wizard\u201d button to get started with VPC creation.<\/p>\n

\"Blog<\/a><\/p>\n

2.<\/p>\n

<\/a>In the next step, you will be prompted to select configuration type of your VPC.
\nConfiguration here lets you select the basic architecture of your VPC , like whether you want to have a single publicly accessible subnet in your VPC or to have separate public and private subnet for security concern.
\nHere we choose VPC with Public and Private Subnets as per our need.
\nClick continue.<\/p>\n

\"Blog<\/a><\/p>\n

3.<\/p>\n

<\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a>Now, put in the information to create a VPC plus its subnets, gateways, and routing tables, NAT Instance type and the Hardware tendency.
\nInside VPC with Internet Gateway, IP CIDR block lets you decide number of private IP that will be available for you inside your VPC. Similarly, give IP CIDR for Public and Private Subnet. Also you can decide the availability zone for each subnet ( here, AP-Southeast-1a for Public Subnet and AP-Southeast-1b for Private Subnet) or leave it Default if you want Amazon to handle it.You can optionally use a network address translation (NAT) instance in a public subnet in your VPC to enable instances in the private subnet to initiate outbound traffic to the Internet, but prevent the instances from receiving inbound traffic initiated by someone on the Internet. So, under NAT instance with Elastic IP Address you can choose an instance type for the NAT (m1. small here) and provide a key pair name that is required for authentication purpose.And at last under Hardware Tendency, if you need your Instance to run on single-tenant hardware, you can choose Dedicated else can choose Default to run your Instance on Shared Hardware.
\nClick Create VPC button to create a custom VPC with providing configuration information.<\/p>\n

\"Blog<\/a><\/p>\n

4.<\/p>\n

Finally, your VPC is configured and ready for launching Amazon services inside it.
\nNow, we will just instantiate an EC2 machine in public subnet which will be accessible as a web server and a mysql RDS instance in private subnet not accessible directly through internet. Also we will connect to the RDS instance through phpmyadmin installed on EC2 instance running in public subnet.<\/p>\n

But before, we must create security groups that will be associated with each instance within the subnets. Lets create security group for our instances in public subnet.<\/p>\n

\"Blog<\/a><\/p>\n

On VPC dashboard , click\u00a0Security Groups<\/em><\/em><\/span><\/p>\n