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:
Convert an existing instance into a cluster
Do not use this release to create new clusters of Splunk SOAR (On-premises).
Use this release to upgrade from your current privileged deployment of Splunk Phantom 4.10.7 or Splunk SOAR (On-premises) releases 5.0.1 through 5.3.4.
If you are upgrading a privileged deployment of Splunk Phantom 4.10.7 or Splunk SOAR (On-premises) releases 5.0.1 through 5.3.4, upgrade to release 5.3.6, convert your deployment to unprivileged, then upgrade again directly to Splunk SOAR (On-premises) release 6.1.1 or higher.
If you have a privileged deployment of Splunk SOAR (On-premises) release 5.3.5, convert your deployment to unprivileged, then upgrade directly to Splunk SOAR (On-premises) release 6.1.1 or higher.
To learn how to upgrade see Splunk SOAR (On-premises) upgrade overview and prerequisites.
If you have an existing instance that you want to turn into a clustered deployment you need to build a new cluster, then restore the PostgreSQL database of your existing instance to your new cluster. The checklist lists the stages and references the topics with detailed instructions.
Number | Task | Description |
---|---|---|
1 | Build a new cluster with external services | Build a cluster using one of the following methods:
|
2 | Back up your current instance. | See Backup a database and restore to an external database in Set up an external PostgreSQL server in Install and Upgrade . |
3 | Restore the PostgreSQL database to the PostgreSQL database for the new cluster. | Backup a database and restore to an external database in Set up an external PostgreSQL server in Install and Upgrade . |
Create a cluster in Amazon Web Services | Run make_server_node.pyc |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.3.6
Feedback submitted, thanks!