Step 3. Configure Routing
If you have created a peering connection between two different VPCs, you must add routes to the route tables associated with the subnets of the accepter and requester VPC to enable private traffic between those VPCs.
To add a route to a route table, do the following:
- In the VPC console, navigate to Virtual Private Cloud > Route tables, choose the route table and click Actions > Edit routes.
- Complete the Edit routes wizard:
- Click Add routes.
- In the Destination field, specify the range of IPv4 addresses to which the network traffic in the peering connection must be directed.
The IPv4 address range must be specified in the CIDR notation (for example, 12.23.34.0/24).
- In the Target field, select the Peering Connection option and specify the ID of the peering connection.
To obtain the ID, you can look it up on the Peering connections page in the VPC console.
- Click Save changes.
Note |
For Veeam Backup for AWS to be able to deploy worker instances based on VPC networks and subnets for which you have created VPC interface endpoints, you will have to add the necessary worker configurations as described in section Managing Worker Configurations. If you do not add specific worker configurations, Veeam Backup for AWS will use either the default or the most appropriate network settings of AWS Regions. |
