The classic playbook editor will be deprecated in early 2025. Convert your classic playbooks to modern mode.
After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
This documentation does not apply to the most recent version of Splunk® SOAR (On-premises).
For documentation on the most recent version, go to the latest release.
Create a cluster from an RPM or TAR file installation
Build a cluster, putting each of the services on its own server or group of servers to serve multiple cluster nodes of .
| Number | Task | Description |
|---|---|---|
| 1 | Create the HAProxy server. | Use the HAProxy server to be a load balancer for the nodes in your cluster. See Set up a load balancer with an HAProxy server. |
| 2 | Create the PostgreSQL server or cluster. | Establish a PostgreSQL database server or cluster to store information. See Set up an external PostreSQL server. |
| 3 | Create the file shares server. | will store all its shared files on the prepared GlusterFS server. You can use NFS or other network file system. Instructions for that are not included in this document. See Set up external file shares using GlusterFS. |
| 4 | Install Splunk Enterprise. | will use Splunk Enterprise for searches and collect data for indexing using the HTTP Event Collector. See Set up Splunk Enterprise. |
| 5 | Install cluster nodes. |
|
Last modified on 24 March, 2022
| Create a cluster from an OVA installation | Create a cluster using an unprivileged installation |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1
Download manual
Feedback submitted, thanks!