Adding Wazuh manager nodes
You can scale the Wazuh manager cluster horizontally by adding worker nodes. Additional nodes share the event load of a larger Wazuh agent fleet. With a load balancer in front of the cluster, agents also keep reporting when one node fails.
Every Wazuh 5.x manager is already a cluster node. A manager installed on its own is a master node with no workers. A new worker turns that master into a multi-node cluster.
Requirements for a new node
A new node joins the cluster only when it matches the master node on these points. A worker that breaks one of the first four requirements doesn't join, and /var/wazuh-manager/logs/cluster.log names the error code.
Requirement |
Why it matters |
|---|---|
The same Wazuh version as the master node. |
The master refuses a worker with a different version (error |
The same |
The master node can't decrypt the messages of a worker node with another key. It logs error 3025 and closes the connection. |
The same |
The master refuses a worker from another cluster (error |
A unique |
The master refuses a duplicate name, its own name, or a name with other characters (errors |
Certificates issued by the root certificate authority (CA) of the deployment. |
Agents trust one CA. A node issued from another CA fails TLS for every agent that reaches it. |
Network access to the master node on TCP port |
Every worker opens its cluster connection to the master on this port. |
The cluster doesn't synchronize /etc/wazuh-manager/wazuh-manager.conf or the certificates in /etc/wazuh-manager/certs/. You configure and provision each node on its own.
Choose the procedure for your deployment
The steps depend on how you installed Wazuh. The difference is where the root CA of the deployment lives and how the Wazuh indexer is exposed.
All-in-one deployment: The Wazuh indexer, Wazuh manager, and Wazuh dashboard run on one endpoint. You installed them with the installation assistant
-aoption or the all-in-one step-by-step guide. See Add a Wazuh manager node to all-in-one deployments.Distributed deployment: The components run on separate endpoints, and the root CA depends on how you installed them. See Add a Wazuh manager node to distributed deployments.
After the new node joins the cluster, put the cluster behind a load balancer so agents reach every node through one address.