This article describes the required steps in order to establish connectivity between Zadara and your AWS Virtual Private Cloud (VPC).
Note: This is a one-time step in the AWS region where you have provisioned your VPSA.
After submitting a VPSA creation request (along with your AWS information) Zadara creates a new virtual interface to link to your account, but for security reasons this connection remains inactive until you confirm acceptance.
- Verify/Create VGW (Virtual Private Gateway)
- Attach Direct Connect Virtual interfaces to your VPC
- Updating the VPC Route Table
Direct Connect Virtual Interfaces must be attached to a VGW (Virtual Gateway).
From your AWS Management Console, open the VPC service (under the upper menu "services" section)
On the left navigation menu, scroll down and open the "Virtual Private Gateways" section.
In case you already have an existing VGW, verify that it is attached to the VPC that will be connected to your VPSA, and proceed to the next step.
In case you do not have a VGW, click on "Create Virtual Private Gateway" - give your VGW a name, and approve its creation.
From the VGW section, select the newly created VGW and attach it to your VPC
Attach Direct Connect Virtual interfaces to your VPC
Now that we have created a VGW, we can accept the Direct Connect Virtual Interfaces offered by Zadara, navigate to the Direct Connect service using the upper menu "Services" section.
If you don't see any pending interfaces make sure you are in the right region. The current region should be displayed in the upper right corner of the AWS console ( the above screen clip shows the Frankfurt region).
Note: If you do not see a specific region, but instead see a single "Global" region ( as per screenclip below). Use the return to the old experience option first before checking your region and continuing.
After confirming correct region - Select the checkbox of the first connection, accept the warning in the south pane, and click "Accept Virtual Interface".
In the confirmation prompt, select your VGW and approve. Repeat the process for the secondary virtual interface. Note it may take up to 10 minutes for the connection become available. In case your Direct Connect refuses to come up - please contact us via firstname.lastname@example.org.
Updating the VPC Route Table
We also need you to adjust the VPC Route table in order to allow proper connectivity to the VPSA.
From the VPC service open the Route Tables option from the menu on the left.
To allow "route propagation" for the VGW; click on the "Edit route propagation" option and select the "Propagate" checkbox.
It can take up to 15 minutes for route propagation to complete. Once it does your route table should have an additional route to Zadara's VPSA network subnet.
That’s it! at this point your VPSA is read to be accessed from within your VPC. In order to manage it, open its Management IP address as described in Zadara's Provisioning Portal.
Reminder - the management IP is accessible only from within your VPC network.