Configuring route tables for VPC peering in API Task AWS account

Routing tables direct the data traffic between the Control Room AWS account and the API Task AWS account through VPC peering connection.

Each VPC in AWS account includes route tables for its subnets. Edit the route tables of workload and node subnets of the VPC to ensure that the data traffic routes through the VPC peering connection. When you deploy the CloudFormation stack in the API Task AWS accounts, the following subnets are created:
  • api-task-workload-1
  • api-task-workload-2
  • api-task-workload-3
  • api-task-nodes-1
  • api-task-nodes-2
  • api-task-nodes-3

Prerequisites

Ensure that you have administrator privileges for the API Task AWS account.

Procedure

  1. Log in to the API Task AWS account console.
  2. Go to VPC > Route table.
    The Route tables table appears.
  3. Click the route table ID link of the api-task-workload-1 route table.
    The route table details of this ID appear with all the configured parameters.
  4. Go to Actions > Edit routes.
    The Edit routes page appears.
  5. Click Add routes and do the following to add the new route table entries:
    1. Enter the CIDR block of the Control Room AWS account VPC in which the Control Room in Destination.
    2. Select Peering connection as the resource type, and then choose the resource ID of the already set up VPC peering connection.
    3. Click Save changes to save the new route.
    This ensures that any data traffic from the API Task AWS account to the Control Room AWS VPC routes through the VPC peering connection. The status of the route changes to Active.
  6. Repeat steps 3 to 5 for the following route tables to complete the route table configuration on the API Task AWS account side:
    • api-task-workload-2
    • api-task-workload-3
    • api-task-nodes-1
    • api-task-nodes-2
    • api-task-nodes-3
Once you configure all the subnet route tables, the VPC peering connection handles all outgoing data traffic from the API Task AWS account to the Control Room AWS account.

Next steps

You must now configure the route tables on the Control Room AWS account to route the incoming data traffic through the VPC peering connection.