How to do it...

1. Log in to your AWS account and open the VPC Dashboard as shown in the earlier recipe.
2. Click on Route Tables under the Virtual Private Cloud menu. We can see the Main Route Table created and associated with the VPC that we created from the console. You can see that no subnet is associated with any route explicitly:

1. Click on Routes. You can see there is only one route with the Target as local. Click on Edit, and then click on Add another route. Add all destinations with 0.0.0.0/0 and target the Internet Gateway that we created earlier. Also, add the NAT Gateway in as another route. Click on the Save button:

1. Go to the Subnet Associations tab. You can see that no subnet is explicitly associated with this route:

1. Click on Edit. The following console will open. Select the subnet that we created from the console. Click on the Save button:

1. You can see that Explicitly Association has been modified from 0 to 1:

1. Let's add another route for creating a private subnet. Click on Create Route Table. The following window will open. Put the Name tag and select the VPC that we created from the console earlier. Click on Yes, Create:

1. We can see the newly created Route Table in the console. However, the Main column is No for this case:

1. Go to Subnet Associations. Click on the Edit button. Choose the other subnet that we created. Click on the Save button:

1. After removing the subnet association with a particular route table, you can delete it by clicking the Delete Route Table button.