In this section, you’ll create the first of two transit gateway route tables in the network-prod
AWS account so that you have control over which of your VPCs can access the site-to-site VPN connection and the infrastructure shared services VPC that you’ll set up in a later section.
Create a transit gateway route table for the site-to-site VPN connection and the infrastructure shared services VPC that you’ll be creating in another section. We’ll refer to this route table as our network services route table.
network-prod
AWS accountManagement console
associated with the AWSAdministratorAccess
role.VPC
Transit Gateway Route Tables
Create Transit Gateway Route Table
Field | Recommendation |
---|---|
Name |
infra-network-services |
Transit Gateway ID |
Select your transit gateway from the list |
Create Transit Gateway Route Table
infra-network-services
route tableavailable
, select the Associations
tab. You might have to refresh the page to see the state change.Create association
Field | Recommendation |
---|---|
Choose attachment to associate |
Choose the transit gateway attachment id for the VPN attachment. For example, infra-dc1-01 |
Create association
Now that you’ve associated the site-to-site VPN attachment with the route table, you need to enable transit gateway to route traffic from the site-to-site VPN connection to the team development VPC. You do this by adding a propagation to your route table. The propagation will propagate the routing information associated with the team development VPC attachment to this route table.
associated
, select the Propagations
tab. You might have to refresh the page to see the state change.Create propagation
Field | Recommendation |
---|---|
Choose attachment to propogate |
Select the transit gateway attachment id for the common team development VPC attachment |
Create propagation
Routes
tab.Adding test and production workload VPCs: As you create your test and production workload VPCs, you’ll attach those to the transit gateway and add a propagation for each attachment to this route table. These propagations will enable traffic from both the site-to-site VPN connection and the infrastructure shared services VPCs to be routed to the workload VPCs.