6.12 Ensure a route table for the private subnets is created


A _route table_ contains a set of rules, called _routes_, that are used to determine where network traffic is directed.

Each subnet in your VPC must be associated with a route table; the table controls the routing for the subnet. A subnet can only be associated with one route table at a time, but you can associate multiple subnets with the same route table.
Once a route table for the private subnet is created, all the subnets which should be private in the Web, App and Data tiers can be associated with the route table.

The route table should only contain the default route ( pointing to the NAT Gateway.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


Using the Amazon unified command line interface:

* Create a route table for your private subnets, and note the RouteTableId in the output:

* aws ec2 create-route-table --vpc-id <application_vpc>

* Associate the new route table with the private subnets:

aws ec2 associate-route-table --route-table-id <route_table_id> --subnet-id <private_subnet1>
aws ec2 associate-route-table --route-table-id <route_table_id> --subnet-id <private_subnet2>

See Also


Item Details


References: 800-53|SC-7(15)

Plugin: amazon_aws

Control ID: 0938341c2d9a238e6468b9d378b3272b3ac90c6c6c7c65dd4ef7591fcd02fbb1