Now that you’ve created a cluster, it’s time to connect your application to your new Apache ZooKeeper cluster. Aside from setting your firewall rules, Instaclustr provides an example (customised to your cluster) to help you through this process.
After your Cluster has finished provisioning, select Details listed under the navigation menu of your Cluster. All your nodes should be in a Running state with no errors listed. Some infrastructure providers allocate both public and private (data center local) IP addresses to cluster nodes. If both are available, they will be listed with their respective nodes on this page.
Note: We suggest that if your application is running within the same data centre as your cluster, you should configure your client to connect to the private addresses. Please refer to your provider’s pricing documentation.
Instaclustr manages the firewall permissions for the nodes in your cluster. Each cluster node only allows connections from one or more trusted IP addresses. You can add one or more trusted IP addresses to the cluster firewall by selecting Firewall Rules from the navigation menu. Under Firewall Rules section, enter any additional IP addresses you wish to trust to the ZooKeeper Allowed Addresses list. Click the Save button when you are finished.
Note: If your cluster is running on AWS and using VPC peering and you would prefer that an AWS security group be allowed to connect rather than individual addresses, please raise a support request.
Instaclustr provides connection information and examples on the Connection Info page which can be accessed by clicking Connection Info under the navigation menu of your cluster.The Connection Info page contains a list of your node addresses, authentication credentials to connect to your cluster and a connection example with a client that Apache ZooKeeper supports. See Command Line for further details.