Skip to main content

IaaS

Tutorial: Connect AWS to CloudConnexa with IPsec using VPG

Abstract

Configure an AWS site-to-site VPN between your VPC and CloudConnexa using a Virtual Private Gateway (VPG), including connector setup, AWS configuration, and connectivity verification.

This tutorial walks you through connecting your AWS VPC to CloudConnexa using an IPsec tunnel with a Virtual Private Gateway.

You'll complete steps in both the AWS Console and the Cloud Connexa Administration Portal. To make this easier to follow, each step is labeled with an icon:

  • ☁️ AWS Console steps — performed in AWS

  • 🔐 CloudConnexa steps — performed in CloudConnexa

To complete this setup, you'll configure:

  • A Customer Gateway to represent the CloudConnexa endpoint.

  • A Virtual Private Gateway attached to your VPC.

  • A site-to-site VPN connection between AWS and CloudConnexa.

  • Tunnel configuration using an AWS-generated configuration file.

Once configured, users and networks connected to CloudConnexa can securely access resources in your AWS VPC.

When to use this setup

Use this configuration when you want to connect a single VPC to CloudConnexa via a virtual private gateway, which only provides access to resources within that VPC. If you need broader connectivity (for example, access to multiple VPCs or public resources), use a Transit Gateway instead. Refer to Tutorial: Connect AWS VPC to CloudConnexa with IPsec using Transit Gateway.

Before you begin

  • Ensure you have a CloudConnexa account and Cloud ID.

  • Ensure you have access to your AWS account and VPC.

  • Ensure your VPC is created and properly configured, including routing and subnets.

🔐 Step 1: Create a Network (CloudConnexa)

  2. Navigate to Networks → Networks.

  3. Click Add Network.

  4. Select at least one Network Scenario. Refer to these tutorials for details:

  5. Click Continue.

  6. For the Network Configuration, enter a name and description (optional).

  7. Select IPsec as the Connector Tunneling Protocol.

  8. For the Connector, enter a name and description (optional).

  9. Click Next.

🔐 Step 2: Select AWS as the platform (CloudConnexa)

In the Network Configuration Wizard, you'll begin configuring your AWS VPC.

2.1 Select the AWS platform

  1. In Platform to Connect, select AWS. Refer to CloudConnexa Connectors and About Network Connectors.

    Instructions will appear on how to configure IPsec connectivity with CloudConnexa.

  2. Review the step-by-step guide.

  3. Click Next.

2.2 Review AWS configuration details

CloudConnexa displays the values required for AWS configuration.

  1. Note the following values from AWS Configuration Details:

    • Target Gateway

    • Virtual Private Gateway / Transit Gateway

    • Customer Gateway

    • Remote Gateway IP Address

    • Certificate ARN

    • Routing Options

    • Static IP Prefixes

  2. You will use these values when configuring AWS resources.

☁️ Step 3: Configure AWS resources (AWS Console)

Set up the required AWS components to establish the IPsec tunnel.

3.1 Create a Customer Gateway

Create an AWS customer gateway as the IPsec endpoint for the CloudConnexa Region.

Note

You can also create the customer gateway while configuring the VPN connection.

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. Navigate to Customer gateways.

  3. Click Create customer gateway.

  4. Enter:

    • Name tag (optional): This creates a tag with a Name key and the value that you specify.

    • BGP ASN: Enter a Border Gateway Protocol Autonomous System Number (ASN) for your customer gateway.

      Note

      The IPsec VPN is going to use static routing. Therefore, the BGP ASN doesn't matter here. You can enter any number here.

    • IP address: Use the CloudConnexa Public IP Address displayed for your network connector configuration.

  5. (Optional) Configure certificate authentication if you'll be using certificate-based authentication. Refer to Creating and managing a private CA.

  6. (Optional) For Device, enter a name for the customer gateway device associated with this customer gateway.

  7. Click Create customer gateway.

3.2 Create a Virtual Private Gateway

To establish an IPsec VPN connection between your VPC and CloudConnexa, create an AWS target gateway. This target gateway will be a virtual private gateway.

  1. Navigate to Virtual private gateways.

  2. Click Create virtual private gateway.

  3. (Optional) Enter a name.

  4. Keep the default ASN.

  5. Click Create.

  6. Select the VPC, then click Actions → Attach to VPC.

  7. Select your VPC and confirm.

3.3 (Optional) Enable route propagation

Turn on route propagation on your AWS VPC route table if you want site-to-site connectivity between your VPC and other private networks connected to CloudConnexa.

  1. Navigate to Route tables.

  2. Select your route table associated with the subnet.

  3. On the Route propagation tab, click Edit route propagation.

  4. Select your new virtual private gateway.

  5. Save changes.

    Routes from your VPN connection are automatically added to the route table and directed to the virtual private gateway when the connection is active.

3.4 Create the VPN connection

  1. Navigate to Site-to-Site VPN connections.

  2. Click Create VPN connection.

  3. Configure:

    • Target gateway type: Select Virtual private gateway, and select the new virtual private gateway.

    • Customer gateway: Select the newly created customer gateway.

    • Routing options: Select Static.

  4. For Static IP Prefixes, copy and paste the Static IP Prefixes displayed on the CloudConnexa Administration Portal's Connector Configuration page, as shown in AWS Configuration Details.

    Note

    The Static IP Prefixes include the Routes of all CloudConnexa Networks configured so far. If you add new Networks or Routes and want site-to-site networking with your VPC, you must update the Static IP Prefixes.

  5. Click Create VPN connection.

3.5 Download the AWS configuration file

  1. Navigate to Site-to-Site VPN connections.

  2. Select your new VPN connection.

  3. Click Download configuration.

  4. Select Generic for the customer gateway device.

  5. Download the file.

    Important

    To properly load the download configuration screen from the AWS Management Console, ensure that your IAM role or user has permission for the following Amazon EC2 APIs: GetVpnConnectionDeviceTypes and GetVpnConnectionDeviceSampleConfiguration.

🔐 Step 4: Configure the Network Connector (CloudConnexa)

In this step, configure the IPsec tunnels on the CloudConnexa side using the AWS configuration.

CloudConnexa supports two tunnels for high availability. You can configure them manually or upload the AWS configuration file.

4.1 Configure CloudConnexa tunnel

  1. Return to the CloudConnexa network wizard configuration.

  2. Select the Authentication Method:

    • Shared Secret: Specify the pre-shared keys (PSK) in each tunnel configuration in the next step.

    • Certificate-based: Upload certificates to apply to all tunnel connectors, and enter the passphrase.

  3. If you select Shared Secret, you can proceed to option 1 and upload an AWS configuration file. For Certificate-based, proceed to option 2 to configure tunnels manually.

Option 1: Upload AWS configuration file (recommended)

  1. Click Upload Generic Configuration File.

  2. Select the configuration file downloaded from AWS.

    CloudConnexa automatically populates the tunnel settings.

Note

AWS creates two tunnels by default. CloudConnexa creates two corresponding Connectors.

Option 2: Configure tunnels manually

If you prefer, you can configure each tunnel manually using the values provided by AWS.

  1. Expand Tunnel 1.

  2. Enter the following:

    • Remote Site Public IPv4 Address: Enter the AWS tunnel endpoint IP address (from AWS configuration, Tunnel 1).

    • Pre-shared Key (PSK): Enter the pre-shared key provided by AWS.

      Important

      You must specify a pre-shared key for each tunnel configuration.

  3. (Optional) Configure advanced settings: Expand Advanced Configuration to customize IPsec parameters:

    • IKE Version: Select the version: IKEv1 or IKEv2.

      Tip

      If using IKEv2 and only GCM encryption algorithms (AES-128-GCM-16 and/or AES-256-GCM-16), the integrity algorithm and a DH group are optional in phase 2.

      For non-GCM encryption algorithms, an integrity algorithm and a DH group are required. The default values are applied automatically.

    • Phase 1 settings:

      Setting

      Description

      Encryption Algorithm

      Select one or more supported encryption algorithms.

      Integrity Algorithm

      Select a supported integrity algorithm.

      Diffie-Hellman Group

      Select a DH group supported by your device.

      Lifetime (sec)

      Enter a value between 901 and 86400.

    • Phase 2 settings:

      Setting

      Description

      Encryption Algorithm

      Select one or more supported encryption algorithms.

      Integrity Algorithm

      Select a supported integrity algorithm.

      Diffie-Hellman Group

      Select a DH group supported by your device.

      Lifetime (sec)

      Enter a value between 900 and 28800.

    • IKE rekey settings:

      Setting

      Description

      Rekey Margin Time (sec)

      Value between 60 and half of Phase 2 lifetime.

      Rekey Fuzz (%)

      Value between 0 and 100.

      Replay Window Size (packets)

      Value between 64 and 2048.

    • Connection behavior:

      Setting

      Description

      Startup Action

      Defines how the tunnel is initiated.

      CloudConnexa Connection Restoration

      Controls whether the tunnel automatically reconnects if interrupted:

      • Defaults to Yes when Startup Action = Start.

      • Automatically set to No when Startup Action = Attach and can't be changed.

      AWS-specific note

      When you set AWS connectors to Attach for the Startup Action, CloudConnexa doesn't initiate the tunnel.

  4. (Optional but recommended) Expand Tunnel 2 and repeat the same configuration steps using AWS Tunnel 2 values.

    Tip

    Using both tunnels provides high availability and failover.

4.2 Verify connectivity

  1. Click Test Connection 1.

    CloudConnexa attempts to establish a connection to your AWS network.

  2. Check the connection status:

    • Connected — The tunnel is successfully established.

    • Offline — The connection failed or hasn't been established yet.

      Tip

      If the connection status is Offline:

      • Click View Logs to review connection details.

      • Verify the following:

        • PSK or certificates match on both sides.

        • IPsec parameters (encryption, DH group, lifetimes) are aligned.

        • Firewall rules allow IPsec traffic.

        • The correct public IP address is configured.

  3. Click Test Connection 2 (if configured).

  4. Check the connection status:

    • Connected — The tunnel is successfully established.

    • Offline — The connection failed or hasn't been established yet.

      Tip

      If the connection status is Offline:

      • Click View Logs to review connection details.

      • Verify the following:

        • PSK or certificates match on both sides.

        • IPsec parameters (encryption, DH group, lifetimes) are aligned.

        • Firewall rules allow IPsec traffic.

        • The correct public IP address is configured.

CloudConnexa attempts to establish a connection to your AWS network.

🔐 Step 5: Complete the Setup (CloudConnexa)

  1. Click Finish to complete the Network configuration.

  2. Confirm that:

    • The Network is created.

    • The Connectors shows a Connected status.

Tutorial: Connect AWS VPC to CloudConnexa with IPsec using Transit Gateway

Abstract

Configure an AWS Transit Gateway VPN between your VPC and CloudConnexa to enable scalable connectivity across multiple VPCs, including routing setup and tunnel configuration.

This tutorial walks you through setting up an IPsec tunnel between your AWS environment and CloudConnexa using a Transit Gateway.

You'll complete steps in both the AWS Console and the Cloud Connexa Administration Portal. To make this easier to follow, each step is labeled with an icon:

  • ☁️ AWS Console steps — performed in AWS

  • 🔐 CloudConnexa steps — performed in CloudConnexa

Use this configuration when you need connectivity across multiple VPCs, shared services, or internet-bound traffic through CloudConnexa.

To complete this setup, you'll configure:

  • A Transit Gateway to act as a central routing hub.

  • A Transit Gateway attachment to connect your VPC.

  • A site-to-site VPN connection between AWS and CloudConnexa.

  • Routing tables for:

    • Your VPC subnets.

    • The Transit Gateway.

  • (Optional) A NAT Gateway for internet-bound traffic from private subnets.

  • Tunnel configuration using an AWS-generated configuration file.

Once configured, users and networks connected to CloudConnexa can securely access resources in your AWS environment.

Overview

In this setup, AWS Transit Gateway acts as a central routing hub that connects:

Compared to a virtual private gateway, a Transit Gateway supports broader and more flexible connectivity.

When to use this setup

Use this configuration when you need connectivity across multiple VPCs or more advanced routing scenarios. If you only need a connection to a single VPC, refer to ???.

Before you begin

  • Ensure you have a CloudConnexa account and Cloud ID.

  • Ensure your AWS VPC and subnets are configured.

  • Ensure you have permissions to create AWS networking resources.

🔐 Step 1: Create a Network (CloudConnexa)

  2. Navigate to Networks → Networks.

  3. Click Add Network.

  4. Select at least one Network Scenario. Refer to these tutorials for details:

  5. Click Continue.

  6. For the Network Configuration, enter a name and description (optional).

  7. Select IPsec as the Connector Tunneling Protocol.

  8. For the Connector, enter a name and description (optional).

  9. Click Next.

🔐 Step 2: Select AWS as the platform (CloudConnexa)

In the Network Configuration Wizard, you'll begin configuring your AWS VPC.

2.1 Select the AWS platform

  1. In Platform to Connect, select AWS. Refer to CloudConnexa Connectors and About Network Connectors.

    Instructions will appear on how to configure IPsec connectivity with CloudConnexa.

  2. Review the step-by-step guide.

  3. Click Next.

2.2 Review AWS configuration details

CloudConnexa displays the values required for AWS configuration.

  1. Note the following values from AWS Configuration Details:

    • Target Gateway

    • Virtual Private Gateway / Transit Gateway

    • Customer Gateway

    • Remote Gateway IP Address

    • Certificate ARN

    • Routing Options

    • Static IP Prefixes

  2. You will use these values when configuring AWS resources.

☁️ Step 3: Configure AWS resources (AWS Console)

Set up the AWS components required for Transit Gateway-based VPN connectivity.

3.1 Create a Transit Gateway

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. Navigate to Transit Gateways.

  3. Click Create transit gateway.

  4. Configure settings as needed.

  5. Click Create transit gateway.

3.2 Create a site-to-site VPN connection

  1. Navigate to Site-to-Site VPN connections.

  2. Click Create VPN connection.

  3. Configure:

    • Target gateway type: Select Transit gateway, and select the new transit gateway.

    • Customer gateway: Select New, and enter CloudConnexa values.

    • Routing options: Select Static.

  4. For Static IP Prefixes, copy and paste the Static IP Prefixes displayed on the CloudConnexa Administration Portal's Connector Configuration page, as shown in AWS Configuration Details.

    Note

    The Static IP Prefixes include the Routes of all CloudConnexa Networks configured so far. If you add new Networks or Routes and want site-to-site networking with your VPC, you must update the Static IP Prefixes.

  5. Click Create VPN connection.

3.3 Attach your VPC to the Transit Gateway

  1. Navigate to Transit Gateway attachments.

  2. Click Create transit gateway attachment.

  3. Select the new transit gateway for the Transit gateway ID.

  4. Configure your transit gateway attachment as needed for your VPC and subnets.

  5. Click Create transit gateway attachment.

3.4 Create a NAT Gateway (for internet-bound traffic)

  1. Navigate to NAT gateways.

  2. Click Create NAT gateway.

  3. Configure the NAT gateway for your VPC and associate it with an Elastic IP.

  4. Click Create NAT gateway.

3.5 Configure VPC route tables

Configure the private subnet route table

This route table is used by resources that don't have direct internet access.

  1. Navigate to Route tables.

  2. Select the route table associated with your private subnet.

  3. Click Edit routes.

  4. Add the following routes:

    • Destination:0.0.0.0/0 → Target: NAT Gateway

    • Destination: 100.96.0.0/11 → WPC Subnet Target: Transit Gateway

      Note

      This is the default WPC Subnet value. You can configure this under Settings → WPC in the CloudConnexa admin portal.

    • Destination: 100.80.0.0/12 → Domain Routing Subnet Target: Transit Gateway

      Note

      This is the default Domain Routing Subnet value. You can configure this under Settings → WPC in the CloudConnexa admin portal.

  5. Click Save changes.

Configure the public subnet route table

This route table is used by resources that can access the internet directly.

  1. Navigate to Route tables.

  2. Select the route table associated with your public subnet.

  3. Click Edit routes.

  4. Ensure the following routes are present:

    • Destination: 100.96.0.0/11 → WPC Subnet Target: Transit Gateway

      Note

      This is the default WPC Subnet value. You can configure this under Settings → WPC in the CloudConnexa admin portal.

    • Destination: 100.80.0.0/12 → Domain Routing Subnet Target: Transit Gateway

      Note

      This is the default Domain Routing Subnet value. You can configure this under Settings → WPC in the CloudConnexa admin portal.

  5. Click Save changes.

Tip

The public subnet typically has a route to an Internet Gateway for internet access. You don't need to modify this configuration for CloudConnexa connectivity.

3.6 Configure Transit Gateway route table

  1. Navigate to Transit gateway route tables.

  2. Click on the route table for your new transit gateway.

  3. Click the Routes tab.

  4. Create the following static routes:

    • 0.0.0.0/0 (default route, points to the VPC resource)

    • 100.96.0.0/11 (WPC subnet, points to the VPN resource)

    • 100.80.0.0/12 (Domain routing subnet, points to the VPN resource)

3.7 Download the AWS configuration file

  1. Navigate to Site-to-Site VPN connections.

  2. Select your new VPN connection.

  3. Click Download configuration.

  4. Select Generic for the customer gateway device.

  5. Download the file.

    Important

    To properly load the download configuration screen from the AWS Management Console, ensure that your IAM role or user has permission for the following Amazon EC2 APIs: GetVpnConnectionDeviceTypes and GetVpnConnectionDeviceSampleConfiguration.

🔐 Step 4: Configure the Network Connector (CloudConnexa)

In this step, configure the IPsec tunnels on the CloudConnexa side using the AWS configuration.

CloudConnexa supports two tunnels for high availability. You can configure them manually or upload the AWS configuration file.

4.1 Configure CloudConnexa tunnel

  1. Return to the CloudConnexa network wizard configuration.

  2. Select the Authentication Method:

    • Shared Secret: Specify the pre-shared keys (PSK) in each tunnel configuration in the next step.

    • Certificate-based: Upload certificates to apply to all tunnel connectors, and enter the passphrase.

  3. If you select Shared Secret, you can proceed to option 1 and upload an AWS configuration file. For Certificate-based, proceed to option 2 to configure tunnels manually.

Option 1: Upload AWS configuration file (recommended)

  1. Click Upload Generic Configuration File.

  2. Select the configuration file downloaded from AWS.

    CloudConnexa automatically populates the tunnel settings.

Note

AWS creates two tunnels by default. CloudConnexa creates two corresponding Connectors.

Option 2: Configure tunnels manually

If you prefer, you can configure each tunnel manually using the values provided by AWS.

  1. Expand Tunnel 1.

  2. Enter the following:

    • Remote Site Public IPv4 Address: Enter the AWS tunnel endpoint IP address (from AWS configuration, Tunnel 1).

    • Pre-shared Key (PSK): Enter the pre-shared key provided by AWS.

      Important

      You must specify a pre-shared key for each tunnel configuration.

  3. (Optional) Configure advanced settings: Expand Advanced Configuration to customize IPsec parameters:

    • IKE Version: Select the version: IKEv1 or IKEv2.

      Tip

      If using IKEv2 and only GCM encryption algorithms (AES-128-GCM-16 and/or AES-256-GCM-16), the integrity algorithm and a DH group are optional in phase 2.

      For non-GCM encryption algorithms, an integrity algorithm and a DH group are required. The default values are applied automatically.

    • Phase 1 settings:

      Setting

      Description

      Encryption Algorithm

      Select one or more supported encryption algorithms.

      Integrity Algorithm

      Select a supported integrity algorithm.

      Diffie-Hellman Group

      Select a DH group supported by your device.

      Lifetime (sec)

      Enter a value between 901 and 86400.

    • Phase 2 settings:

      Setting

      Description

      Encryption Algorithm

      Select one or more supported encryption algorithms.

      Integrity Algorithm

      Select a supported integrity algorithm.

      Diffie-Hellman Group

      Select a DH group supported by your device.

      Lifetime (sec)

      Enter a value between 900 and 28800.

    • IKE rekey settings:

      Setting

      Description

      Rekey Margin Time (sec)

      Value between 60 and half of Phase 2 lifetime.

      Rekey Fuzz (%)

      Value between 0 and 100.

      Replay Window Size (packets)

      Value between 64 and 2048.

    • Connection behavior:

      Setting

      Description

      Startup Action

      Defines how the tunnel is initiated.

      CloudConnexa Connection Restoration

      Controls whether the tunnel automatically reconnects if interrupted:

      • Defaults to Yes when Startup Action = Start.

      • Automatically set to No when Startup Action = Attach and can't be changed.

      AWS-specific note

      When you set AWS connectors to Attach for the Startup Action, CloudConnexa doesn't initiate the tunnel.

  4. (Optional but recommended) Expand Tunnel 2 and repeat the same configuration steps using AWS Tunnel 2 values.

    Tip

    Using both tunnels provides high availability and failover.

4.2 Verify connectivity

  1. Click Test Connection 1.

    CloudConnexa attempts to establish a connection to your AWS network.

  2. Check the connection status:

    • Connected — The tunnel is successfully established.

    • Offline — The connection failed or hasn't been established yet.

      Tip

      If the connection status is Offline:

      • Click View Logs to review connection details.

      • Verify the following:

        • PSK or certificates match on both sides.

        • IPsec parameters (encryption, DH group, lifetimes) are aligned.

        • Firewall rules allow IPsec traffic.

        • The correct public IP address is configured.

  3. Click Test Connection 2 (if configured).

  4. Check the connection status:

    • Connected — The tunnel is successfully established.

    • Offline — The connection failed or hasn't been established yet.

      Tip

      If the connection status is Offline:

      • Click View Logs to review connection details.

      • Verify the following:

        • PSK or certificates match on both sides.

        • IPsec parameters (encryption, DH group, lifetimes) are aligned.

        • Firewall rules allow IPsec traffic.

        • The correct public IP address is configured.

CloudConnexa attempts to establish a connection to your AWS network.

🔐 Step 5: Complete the Setup (CloudConnexa)

  1. Click Finish to complete the Network configuration.

  2. Confirm that:

    • The Network is created.

    • The Connectors shows a Connected status.

Tutorial: Assign DNS servers using DHCP for AWS VPC

Abstract

This tutorial shows how to configure a DHCP option set on your AWS VPC to set the DNS servers for all the resources in your VPC.

This tutorial shows how to configure a DHCP option set on your AWS VPC to set the DNS servers for all the resources in your VPC. Using the DNS server associated with the Connector's tunnel IP address subnet lets your VPC resources access Applications on the WPC using Application Domain-Based Routing.

  1. Create a DHCP option set and configure the Domain name server as the IP address that is one before the tunnel IP address of the Connector. For example, if the tunnel IP address of the Connector is 100.96.1.18, then the DNS server IP address is 100.96.1.17.

    aws_dhcp_options.png

  2. Assign DHCP option set to your VPC.

Tutorial: Find the AWS IPsec tunnel's outside IP address

Abstract

Follow these steps to find the AWS IPsec tunnel's public IP address (Outside IP Address).

To find the AWS IPsec tunnel's public IP address (Outside IP Address), follow the steps below:

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. Click Site-to-Site VPN connections.

  3. Click the hyperlinked Name of the desired VPN connection.

  4. Click the Tunnel details tab.

    AWS_outside_IP_address_of_IPsec_tunnel.png

  5. The Outside IP address will be listed in the Tunnel state section.

Tutorial: Connect Your AWS VPC to CloudConnexa by Deploying a Connector

Abstract

This tutorial shows you the steps to take to deploy a Connector on your AWS VPC. Once deployed, the Connector attempts to establish an outbound OpenVPN tunnel to the configured CloudConnexa Region. On a successful connection, the AWS VPC can be accessed by your CloudConnexa Users.

Launch Connector on AWS

To configure a Network that represents your AWS Virtual Private Cloud (VPC) and install an AWS instance with a Connector that uses AWS CloudFormation, follow these steps:

  1. Sign in to the CloudConnexa Administration portal at https://cloud.openvpn.com

  2. Navigate to Networks and click Networks.

    Select the Scenario(s) that apply to your use case.

  3. Provide a Network Name and enter an optional Description.

  4. Provide a Connector name, select a Region, and click Next.

  5. Select an AWS Region.

  6. Click Launch ad log into AWS.

  7. On the Quick create stack web page, specify the stack details: Stack name, KeyName, SubnetId, VpcId , and then click Next.

    Note

    Use the existing VPC and IP subnet.

  8. Click the I acknowledge that AWS CloudFormation might create IAM resources checkbox to allow CloudFormation to create RouteManagerRole IAM::Role resources. This role configures routes in the VPC Route table to use the Connector. Click Create stack.

  9. Monitor the stack creation as it goes from CREATE_IN_PROGRESS state to CREATE_COMPLETE.

  10. On completion, open the Resources tab to view the created resources. Check that the RouteManagerRole was created along with an InstancSecurityGroup, InstanceProfile, and the EC2Instance.

  11. Click on the Physical ID of the EC2 instance to check its details.

    Note

    The EC2 instance uses Ubuntu. If you want to connect to it with SSH, use ubuntu as the username.

  12. The Connector EC2 automatically connects to the Region and the Network will show up as Online on the Status page of CloudConnexa Admin portal.

A new EC2 instance Security Group is automatically created after the Network Connector deployment through CloudFormation. This Security Group contains only one Inbound Rule to allow SSH connections (Protocol: TCP; Port: 22; Source: 0.0.0.0/0).

Modify existing Security Groups

If you are using Security Groups to protect any instances that need their traffic to be routed through the Connector instance, you need to add the Security Group of the Connector instance to their inbound rules.

This screenshot shows the inbound rules of sg-0d7ffe09b9076d0dd – launch-wizard-1 Security Group are being edited to add the last rule, which accepts all incoming traffic coming from the Security Group sg-0210e0cbe1ce14ee7 that is associated with the Connector instance.

Modify existing Security Groups

Optional: Check and add routes to the VPC Route Table associated with the subnet

Check that a route exists in the route table for the WPC Subnet IP address range configured in Network Settings of CloudConnexa. The default WPC IPv4 subnet address range for CloudConnexa is 100.96.0.0/11. If a route to destination 100.96.0.0/11 using the Connector instance as a target is absent, add it. If other CloudConnexa Networks need to be reached from the VPC, add a route with those Network subnets as the destination and the Connector instance as the target.

The screenshot below shows how the route table should look with an entry for the CloudConnexa WPC IP address subnet (100.96.0.0/11) and an entry for subnet 192.168.0.0/28 which is another Network (for example, office Network) that is reachable via CloudConnexa. Both entries have target as the instance running the Connector.

Note: If you allow CloudFormation to create RouteManagerRole IAM::Role resources, this role will configure routes in the VPC Route table to use the Connector automatically and update the route table as new Networks are added to the WPC.

Check and add routes to the VPC Route Table associated with the subnet

Tutorial: Connect Your Azure VNet to CloudConnexa by Deploying a Connector

Abstract

This tutorial shows you the steps to take to deploy a Connector on your Azure VNet. Once deployed, the Connector attempts to establish an outbound OpenVPN tunnel to the configured CloudConnexa Region. On a successful connection, the Azure VNet can be accessed by your CloudConnexa Users.

Launch Connector On Azure

You can deploy a Connector in the Microsoft Azure environment during the Network creation process. You can choose to either launch a template directly in Azure, or download a template and launch it manually.

62e9c0624b256.png

Steps: Launch a template directly on Azure

  1. Click Launch On Azure.

    • You are redirected to your Azure environment, where a virtual machine (VM) is created automatically.

  2. Define the parameters on the Azure VM, noting that the fields marked with an asterisk are mandatory.

    62e9c0657037e.png

    Parameter

    Value

    Subscription

    A logical container used to provision resources in Azure. It holds the details of all your resources such as VMs, databases, and more.

    Resource Group

    A container that holds related resources for an Azure solution. The resource group includes those resources that you want to manage as a group.

    Region

    The region value propagates from the resource group.

    Disk Type

    The type of storage to be used for your VM disks.

    Admin Username

    The Administrator username for the VM.

    Authentication Type

    The type of authentication to use on the VM. SSH key is strongly recommended.

    Admin Password Or Key

    The SSH key or password for the VM.

    Dns Label Prefix

    The unique DNS label prefix for the public IP that is used to access the VM.

    Vm Size

    The size of the VM.

    Virtual Network Name

    The name of the existing virtual Network (VNet). You can find the VNet name on the Virtual Networks page.

    Subnet Name

    The name of the existing subnet in the VNet you want to use. You can find the subnet name on the Subnets blade of the VNet. This subnet value must be the same as the subnet of the Network on the CloudConnexa Administration portal.

    Network Security Group Name

    The name of the Network security group.

  3. Click Next: Review + create.

    62e9c0675a14e.png

  4. When validation passes, click Create.

    62e9c0694069d.png

The Connector deployment is complete. You can navigate to your resource group to find your VM.

Steps: Launch Connector manually from template

  1. In the CloudConnexa Administration portal, click Download to save the JSON Azure template to your local computer.

    62e9c06bdd7e0.png

  2. Access your Azure portal and click Create a resource.

    62e9c06d1d6aa.png

  3. Search for Template deployment (deploy using custom templates) and click Create.

  4. Click Build your own template in the editor.

    62e9c06ea7c98.png

  5. Click Load File.

    62e9c07083ab6.png

  6. Load the template file from your local computer and click Save.

    62e9c071c9061.png

  7. Follow the steps 2-4 shown in the Steps: Launch a template directly on Azure section to complete the configuration.

Tutorial: Connect Azure to CloudConnexa with IPsec

Abstract

This tutorial shows how to configure an IPsec connection to your Azure VNet. Once configured, site-to-site IPsec tunnel(s) connects your Azure VNet to the configured CloudConnexa Region. On a successful connection, your CloudConnexa users and other networks connected to any of CloudConnexa's Regions can access the Azure VNet.

This tutorial shows how to configure an Azure Site-to-Site IPsec VPN connection between your Azure VNet and a CloudConnexa Region. A good reference for the Azure configuration aspect of this setup is available in Azure documentation.

The Azure configuration involves:

  • Creating a gateway subnet: The virtual network gateway requires a specific subnet named GatewaySubnet. The gateway subnet is part of the IP address range for your virtual network and contains the IP addresses that the virtual network gateway resources and services use.

  • Creating a Virtual Network Gateway: In this step, you create a virtual network gateway (VPN gateway) for your virtual network. Creating one often take 45 minutes or more, depending on the selected gateway SKU.

  • Creating a local network gateway: The local network gateway is a specific object deployed to Azure that represents your CloudConnexa Region for routing purposes.

  • Creating a VPN connection: Create a site-to-site VPN connection between your virtual network gateway and the CloudConnexa Region.

On a successful connection, your CloudConnexa users and other networks connected to any of CloudConnexa's Regions can access the Azure VNet.

  3. Add a Network using the Network Configuration Wizard to represent your AWS VPC and select the IPsec Tunneling Protocol option.

  4. In the Connector configuration step, select Azure from the Platform to Connect drop-down menu. Refer to CloudConnexa Connectors and About Network Connectors.

    Instructions will appear on how to configure IPsec connectivity with CloudConnexa. You will see four steps:

    1. Create Azure Gateways: Use these values when configuring the Azure Local and Virtual network gateways. See steps Step 6 and Step 7.

    2. Setup CloudConnexa Tunnel: Complete the CloudConnexa tunnel setup using values as shown in Step 8 and Step 9.

    3. Create Azure Connection: Use this information in Step 10

    4. Verify Connectivity: After configuring the tunnel on both sides, click “Test Connection” to check that CloudConnexa can establish a connection to the remote network

  5. (Azure) Create a gateway subnet. Refer to Azure documentation. The virtual network gateway requires a specific subnet named GatewaySubnet. The gateway subnet is part of the IP address range for your virtual network and contains the IP addresses that the virtual network gateway resources and services use.

    When you create the gateway subnet, you specify the number of IP addresses that the subnet contains. The number of IP addresses needed depends on the VPN gateway configuration that you want to create. Some configurations require more IP addresses than others. It's best to specify /27 or larger (/26, /25, etc.) for your gateway subnet.

    1. On the page for your virtual network, on the left pane, select Subnets to open the Subnets page.

    2. At the top of the page, select + Gateway subnet to open the Add subnet pane.

    3. Select an appropriate Size. For example, /27.

    4. Click Add.

  6. (Azure) Create a local network gateway. Refer to Azure documentation. The local network gateway is a specific object deployed to Azure that represents the CloudConnexa Region (the site) for routing purposes. You give the site a name by which Azure can refer to it, and then specify the IP address of the site's VPN device to which you create a connection. You also specify the IP address prefixes that are routed through the VPN gateway to the site's VPN device (CloudConnexa Region). The address prefixes you specify are the prefixes located on your on-premises network.

    1. In the Azure portal, go to Local network gateways and open the Create local network gateway page.

    2. Click + Create on the Local network gateways page.

    3. On the Basics tab, fill in the following fields:

      1. Resource Group: Select appropriately.

      2. Region: Select appropriately.

      3. Name: Enter name. For example, CloudConnexa

      4. IP address: Copy from CloudConnexa Admin Portal instructions.

      5. Address Spaces: Copy one-by-one from CloudConnexa Admin Portal instructions.

    4. Click Next to move to the Advanced tab and set Configure BGP settings to NO.

    5. Click Next to move to Review + create tab and click Create.

  7. (Azure) Create a virtual network gateway (VPN gateway). Refer to Azure documentation.

    1. In Search resources, services, and docs (G+/), enter virtual network gateway. Locate Virtual network gateway in the Marketplace search results and select it to open the Create virtual network gateway page. Click + Create.

    2. On the Basics tab, fill in the following fields:

      1. Subscription: Select appropriately.

      2. Name: Enter name.

      3. Region: Select same Region as selected for local network gateway.

      4. Gateway Type: VPN

      5. SKU: Recommend to choose the default setting.

      6. Generation: Recommend to choose the default setting.

      7. Virtual Network: Seclect the one on which the GatewaySubnet was created.

      8. Specify the values for Public IP address. These settings specify the public IP address objects that will be associated to the VPN gateway. A public IP address is assigned to each public IP address object when the VPN gateway is created. Create or use existing Public IP address, enable Enable active-active mode, and create or use an existing SECOND PUBLIC IP ADDRESS.

      9. Set Configure BGP to Disabled.

    3. Click Next: Tags >

    4. Click Review + create to run validation.

    5. After validation passes, select Create to deploy the VPN gateway.

    A gateway can take 45 minutes or more to fully create and deploy. You can see the deployment status on the Overview page for your gateway.

  8. From the Deployment Details section of the Azure Portal's VPN gateway Overview page, copy the two IP addresses and paste it in the Remote Site Public IPv4 Address fields of Tunnel 1 and Tunnel 2 in the Setup CloudConnexa Tunnel section of CloudConnexa Administration Portal.

  9. Create one complex random string for use as PSK and enter it in the Pre-shared Key field for Tunnel 1 and Tunnel 2.

  10. (Azure) Create a VPN connection. Refer to Azure documentation.

    1. At the top of the Connections page, select + Create to open the Create connection page.

    2. On the Create connection page, on the Basics tab, configure the values for your connection:

      1. Under Project details, select the subscription and the resource group where your resources are located.

      2. Under Instance details, configure the following settings:

        1. Connection type: Select Site-to-site (IPSec).

        2. Name: Name your connection. Region: Select the region for this connection.

        3. Region: Same as the previous created entities.

    3. Click Next: Settings >

    4. In the Settings tab, configure the following values:

      1. Virtual network gateway: Select the virtual network gateway from the dropdown list that was created in Step 7.

      2. Local network gateway: Select the local network gateway from the dropdown list that was created in Step 6.

      3. Shared key: The value here must match the value that was entered in Step 9.

      4. IKE Protocol: Select IKEv2.

      5. Use Azure Private IP Address: Don't select.

      6. Enable BGP: Don't select.

      7. IPsec/IKE policy: Select Custom and match all the values for the various fields with what is shown in the CloudConnexa portal. Encryption uses AES256, Integrity uses SHA256, DH Group is 14 and PFS Group is PFS2048. Change IPsec SA lifetime in seconds to 3600.

      8. Use policy based traffic selector: Select Enable.

      9. DPD timeout in seconds: Select 45.

      10. Connection Mode: Select ResponderOnly.

    5. Click Next: Tags>.

    6. Click Review + create to run validation.

    7. After validation passes, click Create and wait till deployment is finished.

  11. Click Test Connection 1 and Test Connection 2 to check connectivity for both the IPsec tunnels.

  12. Continue with the network wizard instructions.

Tutorial: Connect Your GCP VPC to CloudConnexa by Deploying a Connector

Abstract

This tutorial shows you the steps to take to deploy a Connector on your GCP VPC. Once deployed, the Connector attempts to establish an outbound OpenVPN tunnel to the configured CloudConnexa Region. On a successful connection, the GCP VPC can be accessed by your CloudConnexa Users.

Deploy a Connector on GCP

You can deploy a Connector in the Google Cloud Platform (GCP) environment during the Network creation process. You must create a Linux virtual machine (VM) on GCP on which you install the Network Connector.

62e9c0c615763.png

Steps: Install a Linux VM

  1. Navigate to GCP and access Compute Engine > Virtual Machines > VM Instances.

    62e9c0c7d6393.png

  2. Click Create Instance.

    62e9c0c9b6c24.png

  3. Enter the VM parameters.

    62e9c0cb2805c.png
    62e9c0cd16b41.png
    62e9c0cea4dc3.png
    62e9c0d03bc36.png

    Parameter

    Definition

    Name

    The name you assign to the VM.

    Region

    A specific geographical location where your VM is run.

    Zone

    Determines what computing resources are available, and where your data is stored and used.

    Machine family

    The types of VMs for common workloads, optimized for cost and flexibility.

    Series

    The CPU platform series.

    Machine type

    The VM vCPU and memory type.

    CPU platform

    The microarchitecture of your VM instance.

    Container

    Deploy a container to this VM instance by using a container-optimized OS image.

    Boot disk

    Each instance requires a disk to boot from.

    SSH Keys

    Allow access to this instance via SSH.

    Hostname

    The VM instance hostname.

    Network

    The Network determines what Network traffic the instance can access.

    Subnetwork

    Assigns an IPv4 address to the instance from the subnetwork range.

    This subnetwork must be the same as the Network Subnet in the CloudConnexa Administration portal.

    Primary internal IP

    For ephemeral, restarting an instance won't change its internal IP, but deleting and recreating an instance will.

    External IP

    An external IP address associated with this instance. Select an unused static IP address or choose Ephemeral to use an IP from a shared ephemeral IP address pool. Selecting None results in the instance having no external internet access.

    IP forwarding

    IP forwarding must be enabled.

    IP forwarding allows the instance to help route packets.

  4. Click Create.

  5. Click the Select Linux Distribution dropdown and select the distribution that you want to install the Connector on.

    create linux vm.png

  6. Copy the commands shown for your terminal.

  7. Connect to your GCP VM through SSH and paste the commands.

    • Select Yes for each prompt.

    • Once the installation completes, a setup token prompt displays.

  8. In the CloudConnexa Administration portal, click Generate Token and click to copy the token.

  9. Access your Linux terminal and paste the token.

    • The utility imports the Connector Profile and connects to CloudConnexa.

Tutorial: Connect Your GCP VPC to CloudConnexa using IPsec

Abstract

This tutorial shows how to configure an IPsec connection to your GCP VPC. Once configured, a site-to-site IPsec tunnel connects your GCP VPC to the configured CloudConnexa Region. On a successful connection, your CloudConnexa users and other networks connected to any of CloudConnexa's Regions can access your VPC.

This tutorial shows how to configure an IPsec connection to your GCP VPC. Once configured, a site-to-site IPsec tunnel connects your GCP VPC to the configured CloudConnexa Region. On a successful connection, your CloudConnexa users and other networks connected to any of CloudConnexa's Regions can access your VPC.

  3. Add a Network using the Network Configuration Wizard to represent your Cisco private network and select the IPsec Tunneling Protocol option.

  4. In the Connector configuration step, select GCP from the Public Cloud Providers (IAAS)section of the Platform to Connect drop-down menu. Refer to CloudConnexa Connectors and About Network Connectors.

    Instructions will appear on how to configure IPsec connectivity with CloudConnexa.

    You will see three steps:

    1. Create GCP VPN: You must configure the GCP VPN with the information needed to connect to the selected CloudConnexa Region.

    2. Setup CloudConnexa Tunnel: You will provide the Remote Site IP address, configuration, and pre-shared key or certificate to set up the IPsec tunnel.

    3. Verify Connectivity: After configuring the tunnel on both sides, click “Test Connection” to check that CloudConnexa can connect to your network.

  5. Go to the VPN section of Google Cloud Console.

  6. Choose Classic VPN when you Create a new VPN connection.

  7. For the Google Compute Engine VPN gateway, use the settings below:

    1. Name - Enter a valid name.

    2. Network - select the VPC you want to connect to CloudConnexa.

    3. Region - select a GCP Region close to the CloudConnexa Region chosen for the IPsec Connector.

    4. IP Address - create a new one or select an existing static IP address for the VPN Gateway. This is the IP address you will use as the Remote Site Public IPv4 Address in a later step.

  8. For the New Tunnel, use the following settings:

    1. Name - any valid name

    2. Remote Peer Address - enter the one provided in CloudConnexa's Create GCP VPN section of instructions.

    3. IKE Version - IKEv2

    4. IKE pre-shared key - Type in random text and paste it in the Pre-shared Key (PSK) field of CloudConnexa's Setup CloudConnexa Tunnel section.

      Note

      Do not use the Generate and Copy option to generate the PSK key, as the keys it creates may be incompatible with the PSK string validation rules for CloudConnexa.

    5. Routing options - Policy-based

    6. Remote network IP ranges - Enter the one provided in CloudConnexa's Create GCP VPN section of instructions one by one.

    7. Local IP ranges - enter subnets that belong to GCP VPC.

  9. Click Done.

  10. Click Create.

    The created VPN tunnel and CloudVPN gateway will be displayed after a few moments.

  11. In the Setup CloudConnexa Tunnel section, provide your Google Compute Engine VPN gateway public IPv4 address (see, Step 7.d) in the Remote Site Public IPv4 Address text field and the VPN tunnel PSK in the Pre-shared Key (PSK) field (see, Step 8.d).

  12. In the Verify Connectivity section, click Test Connection to check connectivity and click View Logs to see any logs to troubleshoot failures.

  13. Continue with the network wizard instructions.

In this section:
See also: