Creating route table for VPC peering in Control Room AWS account

Once you configure the routing tables on the API Task AWS account to direct the outgoing data traffic through the VPC peering connection, you must configure the routing tables on the Control Room AWS to receive the incoming data through the same VPC peering connection.

Every Control Room running on the AWS EC2 instance requires you to edit the route tables of each of its subnets. If you deploy your Control Room for High Availability in multiple Availability zones, update the subnets in each zone.

Prerequisites

Ensure that you have administrator privileges for the Control Room AWS account.

Procedure

  1. Log in to the Control Room AWS account console.
  2. Go to EC2 > Instances.
    The Instances table appears.
  3. Click the instance ID link of the Control Room.
    The instance summary of this Control Room displays the details of the subnet where the Control Room is available. If you have High Availability Control Room, you must see three subnets below the Subnet ID for each availablility zone.
  4. Click the link that is available below the Subnet ID.
    The link opens the Subnets table of the VPC dashboard and displays the configuration details of the subnet. The route table details appear on the Route table column of the Subnets table.
  5. Click the link that appears in the Route table column.
    The Route tables page appears.
  6. Click the route table ID link that appears in the Route table ID column.
    The link opens the details page of the Route table ID.
  7. Go to Actions > Edit routes.
    The Edit routes page appears.
  8. Click Add routes and do the following to add the new route table entries:
    1. Enter the CIDR block of API Task AWS account 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 the any data traffic from the Control Room AWS account to the API TaskAWS VPC routes through the VPC peering connection. The status of the route changes to state: Status=Active
  9. Repeat the steps on all subnets of every Control Room that are available on the AWS EC2 instances.
Once you configure all the subnet route tables, the VPC peering connection handles all incoming data traffic from the API Task AWS account to the Control Room AWS account.