Deploy Network Connectors to 2 AWS accounts that have no connectivity to each other to enable site-to-site private connectivity between both environments.
Step 1: Deploy a Network Connector to the AWS VPC for AWS Account A. Refer to the AWS VPC connector tutorial.
Step 2: Deploy a Network Connector to the AWS VPC for AWS Account B. Refer to the AWS VPC connector tutorial.
Step 3: Configure routing for both sites: AWS VPC for AWS Account A and AWS VPC for AWS Account B.
Make sure clients from each site can route traffic to other sites and remote clients. To do this, add static routes at the gateway level or to the AWS route tables.
Add routes for the WPC subnets, Domain Routing subnets, and the subnets for other networks. Use the Connector’s private IP address as the target next hop.
Sample routes:
- Default allocated WPC subnets: 100.96.0.0/11.
- Default Domain Routing subnets: 100.80.0.0/12.
- AWS VPC for AWS Account A private subnet: 172.31.16.0/20.
- AWS VPC for AWS Account B private subnet: 10.20.0.0/24.
1. Configure the AWS VPC for AWS Account A route table and add the associated routes.
2. Configure the AWS VPC for AWS Account B route table and add the associated routes.
Comments
0 comments
Please sign in to leave a comment.