CloudConnexa: Connect Two AWS Accounts Using Site-to-Site Networking

Configure routing in AWS accounts so resources in each VPC can communicate through CloudConnexa.

You'll add routes in each VPC that direct traffic for the remote VPC to your local Network Connector.

For this example, we'll use the following subnet ranges:

Note: The AWS VPC ranges are reserved for documentation and aren't intended for actual deployments. Use your VPCs' actual private CIDR ranges and the subnet ranges assigned to your CloudConnexa WPC.

Configure routing for AWS VPC A

First, configure routing in AWS Account A so resources in VPC A can reach VPC B.

1. Sign in to the AWS Management Console for Account A.
2. Navigate to VPC → Route Tables.
3. Select the route table associated with the subnet containing the resources you want to connect to the other VPC.
4. Select the Routes tab, then Edit routes.
5. Add a route with the following settings:
   • Destination: 198.51.100.0/24 (the subnet for VPC B).
   • Target: The network interface of your Network Connector in VPC A.
6. Add routes for your CloudConnexa WPC and Domain Routing subnets if your configuration requires them.
7. Select Save changes.

Your VPC A route table now directs VPC B traffic to the local Network Connector.

Configure Routing for AWS VPC B

Next, configure routing in AWS Account B so resources in VPC B can reach VPC A.

1. Sign in to the AWS Management Console for Account B.
2. Navigate to VPC → Route Tables.
3. Select the route table associated with the subnet containing the resources you want to connect to the other VPC.
4. Select the Routes tab, then Edit routes.
5. Add a route with the following settings:
   • Destination: 192.0.2.0/24 (the subnet for VPC A).
   • Target: The network interface of your Network Connector in VPC B.
6. Add routes for your CloudConnexa WPC and Domain Routing subnets if your configuration requires them.
7. Select Save changes.

Your VPC B route table now directs VPC A traffic to the local Network Connector.

Step 4: Verify network access settings

Before testing connectivity, check that both AWS environments and CloudConnexa allow traffic between the VPCs.

1. In AWS Account A, verify that IP forwarding is configured on the Network Connector and that source/destination checking is disabled on its EC2 instance.
2. Repeat these checks for the Network Connector in AWS Account B.
3. Review the security groups and network ACLs in both AWS accounts. Ensure they allow the traffic you want to exchange between the VPCs.
4. In the CloudConnexa Administration Portal, verify that your Access Groups allow the intended communication between the two Networks.
5. Confirm that both Network Connectors are connected to CloudConnexa.

Verify connectivity

Test the connection in both directions to confirm that resources in the two AWS accounts can communicate.

1. Connect to an EC2 instance in VPC A.
2. Test connectivity to the private IP address of a resource in VPC B.
3. Connect to an EC2 instance in VPC B.
4. Test connectivity to the private IP address of a resource in VPC A.
5. Verify that the applications or services you want to access are reachable across the connection.

If connectivity fails, check the AWS route tables, security groups, network ACLs, CloudConnexa Access Groups, and Network Connector status.

Note: If you're testing with ping, ensure that your security groups and host firewalls allow ICMP traffic. Otherwise, test using a protocol and port permitted by your configuration.