Skip to main content

OpenVPN Support Center

Welcome to the new and improved OpenVPN Support Center.

Search the Support Center

CloudConnexa: Connect Azure and AWS VPCs Using CloudConnexa

  • Updated

Overview

Deploy a Network Connector to both an Azure virtual network (VNet) and an AWS virtual private cloud (VPC) to provide secure, private connectivity between the two environments through CloudConnexa.

Before you begin

Before starting, ensure you have:

  • A CloudConnexa WPC
  • An Azure VNet
  • An AWS VPC
  • Permissions to deploy Network Connectors in both environments

Step 1: Deploy a Network Connector to Azure

Deploy a Network Connector to the Azure VNet. For instructions, see:

Step 2: Deploy a Network Connector to AWS

Deploy a Network Connector to the AWS VPC. For instructions, see:

Step 3: Configure routing

Configure routing so that Azure, AWS, and remote CloudConnexa users can reach each other's private resources.

  1. Add static routes to the Azure route table and the AWS VPC route table. For each route:

    • Use the appropriate CloudConnexa subnet or remote network subnet as the destination.

    • Use the Network Connector's private IP address as the next hop.
      Typical routes include:

      Destination Example
      WPC subnet 100.96.0.0/11 (default)
      Domain Routing subnet 100.80.0.0/12 (default)
      Azure private subnet 10.5.0.0/20
      AWS private subnet 203.31.16.0/20

Azure

Enable the Azure route table and add the required routes:

AWS

Update the AWS VPC route table and add the required routes:

Verify connectivity

After configuring the routes:

  • Verify that Azure resources can reach AWS resources.
  • Verify that AWS resources can reach Azure resources.
  • Verify that CloudConnexa users can access resources in both environments.
     

Comments

0 comments

Please sign in to leave a comment.