I want to make a cluster system within an AWS enterprise. The cluster will have a master node and several slaves. The slaves will connect to the master using a TCP/IP connection. There may be several clusters in our organization's AWS enterprise (eg dev1, dev2, qa1, qa2, etc).
For this particular technology, the slaves must somehow discover the IP address of the master node. What is the best practice in doing this? I had a few ideas:
- Put the entire cluster in some sort of NAT'd subnet and have the master node always at a known address (eg 192.168.0.1)
- Require some sort of domain name for each cluster and use DNS.
- Use Eureka instead of DNS.
There may be more ideas. I'm somewhat new to AWS but not new to network topologies, so I may be going in the wrong direction. #1 about sounds to be the easiest thing to do. Are there any other ideas?