The Details Tab – Configuring Infrastructure Security – SCS-C02 Study Guide

The Details Tab

The Details tab provides a high-level overview of data surrounding the route table, detailing which VPC it resides in, the account owner ID, the route table ID, and any explicit associations, as shown in the following screenshot.

Figure 10.14: The Details tab

These explicit associations relate to any subnets that have been configured to use this route table using the Route Table tab within the subnet configuration. Whenever you create a new subnet, it will automatically use the main route table created by your VPC. However, as mentioned earlier, you can create different route tables. If you configured your VPC to use one of these new route tables, it would be implicitly associated.

The Routes Tab

This tab shows the actual routes that are in place to direct traffic and contains several different fields, as shown here:

Figure 10.15: The Routes tab

The following points will take you through these fields one by one:

  • Destination: This shows a CIDR block range for a network that your traffic needs to route to.
  • Target: This is a gateway that allows you to reach the destination. In this example, you have a route with a destination of 0.0.0.0/0. This destination is used to imply any destinations unknown by the route table (for example, an internet address). The Target value for this route is igw-00cef31fb7078b315, which is an ID for an IGW. This route means that, for any destination not listed within the route table that resides outside of your subnet, you use the IGW to get that address.
  • Status: This shows the status of your routes within the table—for example, Active.
  • Propagated: Route propagation is used when working with a virtual private gateway (VPG), which can automatically propagate routes if configured to do so; this implies that you don’t need to enter VPN routes to your route tables manually.

When routes are added to the route table, you must ensure that the correct subnets use the right table. This is achieved by configuring the subnet associations. The next section discusses this.

The Subnets Associations Tab

This tab shows any explicit subnet associations with this route table that have taken place, along with any subnets within the VPC that are using the main route table.

Figure 10.16: The Subnet associations tab

You can have multiple subnets associated with a single route table, but only a single route table can be associated with a subnet.

The Route Propagation Tab

If you have a VPG configured, you can configure the route propagation setting on the Route propagation tab shown in the following figure.

Figure 10.17: The Route propagation tab

Route propagation allows the automatic population of detected routes across your VPN connection, which helps ensure that the correct routing is in place between your gateways.

Note

As with all AWS resources, you can also set up key-value pairs associated with your route table using the Tags tab.

Now that you have reviewed the route tables, the next thing to cover will be NACLs, which help restrict traffic at a subnet level.