Splunk® SOAR (On-premises)

Install and Upgrade Splunk SOAR (On-premises)

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:
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.

Install using the Amazon Marketplace Image

Install for AWS from the AWS Marketplace in the security category.

The AMI version of is for an unprivileged installation, meaning the the application runs under the phantom user account, and not as root.

  • The base installation directory for the unprivileged AMI is /opt/phantom/.
  • The AMI uses a custom HTTPS port of 9999. A firewalld forwarding rule routes traffic directed to the standard HTTPS port 443 to the custom HTTPS port 9999.

Prerequisites

Your AWS instance must meet or exceed the requirements for either an evaluation system for evaluation or Proof of Value testing, or a production system for production use, and must include:

If you need to connect your organization's on-premises infrastructure to an installation of Splunk SOAR (On-premises) hosted in AWS, consult the article Connect Your Data Center to AWS on the AWS web site.

Federal Information Processing Standard (FIPS) support

can be deployed in a FIPS compliant mode, if the operating system kernel is in FIPS mode.

  • Your operating system, either RHEL or CentOS must be in FIPS mode.
  • You must create a new, unprivileged deployment of , either as a single instance or as a cluster.

Information about setting up RHEL 7.x or CentOS 7.x in Federal Information Processing Standard (FIPS) mode can be found in the Red Hat Security Guide in Chapter 9.

Installation

Perform the following tasks to install :

  1. Log in to your AWS EC2 account.
  2. From your EC2 dashboard, select Launch Instance.
  3. In the AWS Marketplace, search for .
  4. On the Amazon Machine Image entry, click Select.
  5. Click Continue.
  6. Select an instance size. The default is m5.xlarge. does not support using instances smaller than t2.xlarge.
  7. Click Next: Configure Instance Details.
  8. Configure the instance according to your organization's policies.
  9. Click Next: Add Storage.
  10. Add storage.

    You can increase disk size later, but you cannot decrease disk size.

  11. Click Next: Add Tags.
  12. Add tags to help identify your installation in your EC2 dashboard.
  13. Click Next: Configure Security Group.
  14. Configure Security Groups. By default, SSH, HTTP, and HTTPS are permitted from all IP addresses. Increase security by limiting access to your organization's IP addresses.
  15. Click Review and Launch.
  16. Generate or choose SSH keys.

    The SSH user account is phantom. This user account has sudo access for elevating to root.

  17. Click Launch Instances. The installation typically takes 15 minutes to complete.

Next step: log in to verify the installation

You can log in to the web interface after the setup script completes to configure user accounts and additional settings. See Log in to the web interface.

Last modified on 19 September, 2023
FIPS compliance   Install as a privileged user

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2, 5.3.3, 5.3.4, 5.3.5

Acrobat logo Download manual
Acrobat logo Download this page

Was this topic useful?







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