Splunk® SOAR (On-premises)

Install and Upgrade Splunk SOAR (On-premises)

Acrobat logo Download manual as PDF


The classic playbook editor will be deprecated soon. 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:
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.
Acrobat logo Download topic as PDF

Upgrade an unprivileged cluster

Perform the following tasks to upgrade your unprivileged cluster.

If you have already downloaded and extracted the installer package to migrate your privileged instance to unprivileged, you can move straight to step 10 and run the install script.

For each cluster node, follow the upgrade instructions, one node at a time:

  1. Read upgrade overview and prerequisites.
  2. Prepare each cluster node for upgrade. See Prepare your Splunk SOAR (On-premises) deployment for upgrade.
  3. Restart the operating system if you did not recently restart it as part of the preparations in Step 2.
    This step is required to ensure that the upgrade completes successfully and efficiently.
    As the root user:
    reboot
  4. After the system restarts, log in to the operating system as the user that owns Splunk SOAR (On-premises). Do not perform the upgrade as the root user.
  5. Download the unprivileged installer from the Splunk SOAR site. The unprivileged installer prepackages its dependencies and can be installed on systems that cannot reach out to the internet.
    The unprivileged installer is named in the format splunk_soar-unpriv-<major>.<minor>.<patch>.<build>-<commit_short_sha>-<os>-x86_64.tgz.
  6. Conditional: If you have previously upgraded this instance of Splunk SOAR (On-premises), you may still have a directory at <$PHANTOM_HOME>/splunk-soar. If that is true, remove that directory.
    rm -rf <$PHANTOM_HOME>/splunk-soar
  7. Extract the TAR file you downloaded into the Splunk SOAR (On-premises) installation directory.
    tar -xvf <installer>.tgz -C <$PHANTOM_HOME>
    This creates a new directory in the Splunk SOAR (On-premises) home directory, <$PHANTOM_HOME>/splunk-soar.
  8. Make sure that that your current installation of is running.
    <$PHANTOM_HOME>/bin start_phantom.sh
  9. Change directory to the <$PHANTOM_HOME>/splunk-soar directory.
    cd <$PHANTOM_HOME>/splunk-soar
  10. The installer package you extracted creates a file called soar-install in the <$PHANTOM_HOME>/splunk-soar directory. Run that script:
    ./soar-install --upgrade --with-apps

    You can see the full list of arguments for the soar-install script by using the --help option.

  11. After the upgrade is complete, remove installation package by deleting the <$PHANTOM_HOME>/splunk-soar directory.
    rm -rf <$PHANTOM_HOME>/splunk-soar
Last modified on 02 October, 2023
PREVIOUS
Upgrade a Splunk SOAR (On-premises) instance
  NEXT
Migrate a Splunk SOAR (On-premises) install from RHEL 7 or CentOS 7 to RHEL 8

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.4.0, 5.5.0, 6.0.0


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters