Description: This guide explains how to modify an existing AWS IPsec tunnel configured with a Virtual Private Gateway (VPG) to connect to a different CloudConnexa region or Gateway IP address.
Sign in to the CloudConnexa Administration Portal and go to Networks.
Select your network, navigate to Connectors tab, and select Add Connector.
Select the target CloudConnexa region. Below example uses Tokyo.
On the newly created Connector, select Configure to open the Configure Connector page.
Select AWS as the platform, then select Next.
Copy the CloudConnexa public IP address. You’ll use this IP address to create a new Tunnel.
Note: Click the down arrow to view the list of CloudConnexa IP addresses for this region that you can use to establish an IPsec session.Sign in to the AWS portal and go to VPC > Virtual Private Network (VPN) > Site-to-Site VPN connections. Select Create VPN Connection and configure the following settings:
Name: Enter a name for the new VPN Connection.
Target Gateway Type (Virtual Private Gateway): Select the corresponding Virtual Private Gateway.
Customer Gateway (New): Enter the CloudConnexa public IP address you copied in step 6.
Routing Options (Static): Enter the CloudConnexa WPC and domain routing subnets, including any other CloudConnexa networks that need access to the AWS network. You can also find this network and subnet information under "Static IP Prefixes” on the CloudConnexa Connector IPsec setup page.
Select Create VPN Connection.
Note: Ensure that the new site-to-site tunnel replicates the same configuration and settings as the current active site-to-site tunnel.
Select the new Site-to-Site VPN connection you created, then select Download configuration. Select Generic as the vendor and IKEv2 as the IKE version.
Upload the downloaded configuration file to the CloudConnexa IPsec configuration.
Select Finish.
Once the New Connector is Online and working, proceed to delete the Old Connector both at CloudConnexa Portal and its corresponding Site-to-Site VPN Connections at AWS.
Comments
0 comments
Article is closed for comments.