CloudConnexa: Connect Google Cloud and AWS VPCs Using Site-to-Site Networking

Configure routing in both cloud environments so resources in each VPC can communicate through CloudConnexa.

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

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

Note: The Google Cloud and AWS subnet 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 the Google Cloud VPC

First, configure routing in Google Cloud so resources in your Google Cloud VPC can reach the AWS VPC.

1. Sign in to the Google Cloud console.
2. Navigate to VPC network → Routes.
3. Select the Route management tab.
4. Select Create route.
5. Configure the route with the following settings:
   • Name: Enter a descriptive name, such as 'to-aws-vpc'.
   • Network: Select the VPC containing your Google Cloud Network Connector.
   • Destination IP range: Enter 198.51.100.0/24 (the subnet for the AWS VPC).
   • Priority: Use the appropriate route priority for your environment.
   • Next hop: Select the next-hop IP address option and enter the internal IP address of your Google Cloud Network Connector.
6. Select Create to save the route.
7. Add routes for your CloudConnexa WPC and Domain Routing subnets if your configuration requires them. Use the same Network Connector as the next hop.

Your Google Cloud VPC now has a route directing traffic for the AWS VPC to the local Network Connector.

Configure Routing for the AWS VPC

Next, configure routing in AWS so resources in your AWS VPC can reach the Google Cloud VPC.

1. Sign in to the AWS Management Console.
2. Navigate to VPC → Route Tables.
3. Select the route table associated with the subnet containing the resources you want to connect to the Google Cloud 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 the Google Cloud VPC).
   • Target: The network interface of your AWS Network Connector.
6. Add routes for your CloudConnexa WPC and Domain Routing subnets if your configuration requires them.
7. Select Save changes.

Your AWS VPC route table now directs traffic for the Google Cloud VPC to the local Network Connector.

Step 4: Verify network access settings

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

1. In Google Cloud, verify that IP forwarding is enabled for the VM instance running your Network Connector.
2. In AWS, verify that IP forwarding is configured on the Network Connector and that source/destination checking is disabled on its EC2 instance.
3. Review your Google Cloud firewall rules, AWS security groups, and network ACLs. 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 Google Cloud and AWS can communicate.

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

If connectivity fails, check the Google Cloud and AWS routes, Google Cloud firewall rules, AWS 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.