For an overview on VPC Peering see the AWS VPC Peering Guide. Instaclustr supports VPC peering as a mechanism for connecting directly to your Instaclustr managed cluster. VPC Peering allows you to access your cluster via private IP and makes for a much more secure network setup.
Note: If you only intend to connect to your cluster from a peered VPC, then choose broadcast private IP address when you create a new cluster. If you're peering to an existing cluster, contact support to change the nodes' broadcast address. If you intend to connect from both the peered VPC and other sources then contact support for an explanation of the options and their implications.
2. Once you are on the Cluster Settings page, click the VPC Peering Settings... button.
3. Fill in the required information on the VPC Peering Connections and click Submit VPC Peering Request ...
This form requires:
Note: You will need to explicitly assign the route you created to the subnet of the instances that need to access the peering connection. You can do this by:
- Checking the instance details to find its subnet
- Copying the subnet ID
- Navigating to the VPC section and filtering the Subnets for the copied ID
- Click on the "Route Table" tab and change the assigned route table to the new route table
Once the new route table has been assigned to your subnet, the "Main" column will change to "yes".
We automatically generate the routes within our VPC to ensure traffic is routed correctly to your VPC. Once you have accepted the peering request, the VPC peering connection will show up as active in your Instaclustr dashboard.
4. Once you have accepted the peering request, the VPC Peering Settings page will show the peering connection as active.
Note: To test the peering succeeded, you may try netcat or telnet. Port 9042 is the exposed port for CQL:
nc -z <node_private_address> 9042; echo $?
telnet <node_private_address> 9042