Splunk® SOAR (On-premises)

Install and Upgrade Splunk SOAR (On-premises)

As of version 6.4.0, the visual editor for classic playbooks is no longer part of Splunk SOAR. Before upgrading, convert your classic playbooks to modern mode. Your classic playbooks will continue to run and you can view and edit them in the SOAR Python code editor.
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.

Log in to the web interface

Perform the following tasks to log in to the web interface after installation is complete.

  1. Using a web browser, go to the IP address you assigned to .
    • If you installed as an unprivileged user, log in to 's web interface at the custom HTTPS port. 
      https://<ip address or hostname>:<your https port>

      The custom HTTPS port for unprivileged OVA or AMI based installations is 9999. However, the UI is still accessible on port 443.

    • If you installed from the AWS Marketplace, get the public IP address for the instance from the EC2 Management Console and the full AWS instance ID for the EC2 instance. Log in to the web interface by using the public IP address.
  2. Log in using the default credentials. Use admin as the username and password as the password. If you installed from the AWS Marketplace, use admin as the username and the full AWS instance ID as the password.

    AWS requires about 20 minutes to complete the setup. After the setup is complete, you can use your full AWS instance ID as the password. Attempting to login before that will result in a login error.

  3. Change the admin user's password:
    1. Click the user name admin, then select Account Settings.
    2. Click the Change Password tab.
    3. Type the current password.
    4. Type a new password.
    5. Type a new password a second time to confirm.
    6. Click Change Password.

Log in to Splunk SOAR (On-premises) using SSH

To SSH into the instance perform the following steps:

  1. Open a terminal window.
  2. SSH to your instance's operating system ssh phantom@<hostname or IP address of >.

Remote SSH is disabled for the root user. The accounts user and phantom have sudo permissions. You can use the account user to administer the operating system.

In order to log in to the operating system of your AMI-based installation using SSH, use the user id phantom. If you need root access, use sudo su -.

Opening TCP port 443 on unprivileged deployments

If you have installed an unprivileged deployment of , TCP port 443 is inaccessible. This is because root privileges are required to open port 443. If you would like HTTPS traffic to be forwarded from the port you defined during install to port 443, follow these steps:

  1. SSH to the instance with the user account phantom.
    ssh phantom@< hostname or IP address>
  2. Elevate to root.
    sudo su -
  3. Configure port forwarding using the port_forward tool.
    <PHANTOM_HOME>/bin/phenv port_forward configure
Last modified on 31 January, 2023
Install as an unprivileged user   About clusters

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

Acrobat logo Download manual
Acrobat logo Download this page

Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

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