AWS VPC Peering

Hydrolix automatically creates a new VPC based on the Client ID you received:
hdxcli-xxxx

You can search for your ClientID in the VPC services like that:

AWS VPCAWS VPC

As you can see we use by default the following subnet:
10.0.0.0/16

Take a note of the VPC ID you'll need it for the peering.

In order to enable VPC Peering with another VPC in your account you need to make sure that the subnet don't overlap.

In my example I'm using the default VPC on AWS where I've got my Kafka deployed, I'll use VPC Peering to pull data from Kafka using Hydrolix Cluster.

The first thing to setup is the actual VPC Peering connection:

VPC PeeringVPC Peering

You will select the Hydrolix VPC ID and the other one you want to use like that:

Peering CreationPeering Creation

Once you approved the peering connection you need to keep your peering connection ID to use it later on.

Modify your routing table

Now that we have our peering connection available, we need to modify our routing table to add a route to the IP required.

In my example I've got Kafka running on 2 IPS:

  • 172.31.33.113
  • 174.31.33.174

First I need to find my main routing table for my VPC click on route tables and search for your VPC.

You'll have several routing table select the main one like in the image bellow:

Route TableRoute Table

Click on the Routes button and add a new route, you will see an interface similar to this:

Peering CreationPeering Creation

Add the IP your Kafka is running and select target Peering Connection this will list the peering connection we created earlier.

Hydrolix has now a route to your Kafka, don't forget to update your security group to allow the data pull and update the ACLs.

We now need to do the same from our default VPC, select your routing table from the VPC where Kafka is running and modify the routing table to add an entry to allow communication to your Hydrolix cluster.
As we noticed Hydrolix is using 10.0.0.0/16 so here I'm adding this subnet in my routing table and I specify again the Peering Connection created earlier:

Route Main VPCRoute Main VPC

We now have a full bi-directionnal communication.


Did this page help you?