Are you looking at our ELK multi-cluster example and seeing that it doesn’t appear to deploy
coordinating nodes? If so - you would be correct! For the example, we deploy an Elasticsearch cluster where every node is both a
master as well as a
data node to keep the example simple. As an aside,
coordinating nodes is another name for
master nodes. See here
The way that you determine what kind of Elasticsearch node you are deploying is by modifying the Elasticsearch yml configuration file. See the section I’ve highlighted in our example config file.
Our multi-cluster example code brings up one Elasticsearch cluster where each node is both a
master and a
data node. In production, you would use our Elasticsearch Cluster module two times with two different configuration files. One of the configuration files would create a
data only Elasticsearch cluster while the other would create a
master only cluster.
The two “instances” of the Elasticsearch-cluster module would automatically auto-discover one another because we’re using the EC2 auto-discovery plugin for Elasticsearch. It’s configured here.
Now, when we deploy our reference architecture, if customers request a self managed ELK stack, then for their production environments we deploy exactly what I described above: two instances of Elasticsearch-cluster with slightly different config files instructing them to be
data nodes in one case and
master nodes in the other.
Let me know if that helps!