Due to RightScale Legacy Platform deprecation, this section covering Amazon Web Services Virtual Private Clouds (VPC) is no longer valid. Please see the Network Manager section for current information on creating and managing AWS VPCs.
A default route table is created whenever you create a VPC and automatically becomes the Main route table. In this setup example, you can designate this route table as the route table for the public VPC subnets. Because you are also using private VPC subnets, you also need to create a private route table. After creating the appropriate route tables, you can then set up routing for your subnets.
Go to your VPC (Clouds > AWS Region > VPCs > your VPC).
Click on Route Tables. The default route table is already in the list of route tables with all of the subnets associated to it.
Change the name of the existing route table by clicking -changeme- and changing the name to Public.
Click New to create the route table. Change the Name to Private
Associate each private subnet to the private route table.
In the Route Table list, click the first subnet you created (for example, private-a) in the Associations column.
Click Associate Route Table and select Private from the VPC Route Tables list
Repeat steps b and c for each private VPC subnet.
Set up routing for each subnet. The public route table uses the Internet gateway that you set up previously. The private subnet routes to the NAT/Bastion host that you configured previously.
In the Route Table list, click on the Public VPC Route Table.
Click the Route Set tab.
Under New Route, change the CIDR IP to 0.0.0.0/0 (any ip address) and add the internet gateway you created previously.
Click the Route Set tab.
In the New Route Area change the CIDR IP to 0.0.0.0/0 (any IP address) and add the VPC NAT server that you created previously.
The following screen shows the completed Route Tables.
After you complete the setup and configuration of your VPC and get your NAT Host running, you can start building your deployment. Be sure to pick the correct subnets for each server that you add; load balancers or any server that is reached from the internet must be in one of the public subnets and have an Elastic IP associated to it while servers in the private subnets do not use Elastic IPs.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.