Upgrade path for Splunk SOAR (On-premises) unprivileged installations
Unprivileged deployments of Splunk Phantom or Splunk SOAR (On-premises) have a more streamlined upgrade path than privileged deployments.
Upgrade paths:
- Unprivileged Splunk Phantom deployments running a release earlier than release 4.10.7 must be upgraded incrementally from release to release, until Splunk Phantom release 4.10.7.
- Unprivileged Splunk Phantom deployments running release 4.10.7 can be upgraded directly to Splunk SOAR (On-premises) release 6.2.1, then can upgrade to release 6.3.0.
- Unprivileged Splunk SOAR (On-premises) running a release earlier than release 6.2.1 can be upgraded to Splunk SOAR (On-premises) release 6.2.1, and then to release 6.3.0.
- Deployments running on the CentOS 7 operating system must migrate to a supported operating system before they can upgrade beyond release 6.3.0.
- Deployments running on Amazon Linux 2 are encouraged to migrate to Amazon Linux 2023. See Migrate a Splunk SOAR (On-premises) install from Amazon Linux 2 to Amazon Linux 2023.
CAUTION: All deployments must upgrade to Splunk SOAR (On-premises) 6.2.1 before upgrading to higher releases in order to upgrade the PostgreSQL database. PostgreSQL databases local to the SOAR deployment are updated to PostgreSQL 15.x during the upgrade process. The PostgreSQL database for all clustered deployments, or deployments using an external database must be upgraded manually.
If your Splunk SOAR (On-premises) deployment is running on the CentOS operating system, you must migrate the deployment to a supported operating system before you can upgrade beyond release 6.3.0.
A list of important or breaking changes and the versions where those changes occur is in Splunk SOAR (On-premises) upgrade overview and prerequisites. Review that list before upgrading.
Upgrade path table
Look on the following table to find your currently installed Splunk Phantom or Splunk SOAR (On-premises) release to see your complete upgrade path.
| Starting version | Path to current version | Details |
|---|---|---|
| 4.6.19142 |
|
|
| 4.8.24304 |
|
|
| 4.9.39220 |
|
|
| 4.10.0 - 4.10.6 |
| See:
|
| 4.10.7 |
|
|
| 5.0.1 - 6.1.0 |
|
|
| 6.1.1 |
|
|
| 6.2.0 |
|
|
| 6.2.1 |
|
|
| 6.2.2 |
|
|
| 6.3.0 |
|
|
| 6.3.1 |
|
|
| 6.4.0.90 |
|
Note: If you previously upgraded to release 6.4.0.90, you should either patch your instance of 6.4.0.90 or upgrade to release 6.4.0.92 to correct a potential Automation Broker issue. For patching instructions, see https://splunk.my.site.com/customer/s/article/SOAR-6-4-0-90-on-prem-Automation-Broker-patch
|
Example
To upgrade from Splunk Phantom release 4.6 to Splunk SOAR (On-premises) 6.4.0:
- Upgrade your Splunk Phantom to release 4.8.24304
- Upgrade Splunk Phantom to release 4.9.39220
- Upgrade Splunk Phantom to release 4.10.7.63984
- Upgrade to Splunk SOAR (On-premises) release 6.2.1
- Upgrade to Splunk SOAR (On-premises) release 6.3.0
- If needed, migrate from CentOS to a supported operating system.
- Upgrade to 6.4.0.92
- (Conditional) If needed, migrate to a supported operating system.