Cloverleaf Cloud connecting to AWS cluster on different subnets

[Bill Pitts]

Hi

Having an issue connecting an outbound thread from Cloverleaf to an AWS cluster

We’re running Cloverleaf v19.1.2 on Infor’s cloud

Downstream vendor has two physical nodes hosted in AWS cloud, each on a different subnet [AWS stating this is the proper way to do the clustering].

We can connect to the AWS cluster IP and connect when vendor running on node1
If vendor fails over to node2 then we lose connectivity and can’t connect
Connects fine if they fail back over to node1

AWS told us to connect using DNS name as opposed to IP address
We did that and have the same issues – can connect if vendor running on node1, cannot if vendor running on node2

Noticed in feedback from AWS that they have the DNS name associated with two IP addresses – a) IP address for node1 cluster (not physical node1 server) and b) separate IP address for node2 cluster (not physical node2 server)

Example:
Cluster DNS: “DNSname” ClusterIP#1: 1.2.3.4 ClusterIP#2 5.6.7.8
Node IP#1: 1.2.3.5 Node IP#2: 5.6.7.9

Currently I believe our firewall is only allowing traffic to ClusterIP#1 (1.2.3.4). Thinking if we enable the IP for node2 cluster [5.6.7.8] on our firewall we might be able to connect to cluster via DNS name, no matter which cluster IP the DNS is running under… but I’m not sure we can have a DNS name associated with two separate IP addresses.

We’re also looking into connecting with AWS Load Balancer and routing to individual nodes that way but that potentially requires major configuration changes by downstream vendor

Question: has anyone else run into this situation or successfully connected to an AWS cluster running nodes under two separate subnets?

 

Thanks

Topic

[Paul Stein]

Have connected to clustered AWS nodes but not on different subnets. However I agree, add the node2 network to your vpn encryption domain, or else the dns will not resolve when they are running on node 2.

[Author]

Replies