Splunk SOAR

DNS error when logging in to Splunk SOAR instance deployed on an AWS EC2 instance

sschimper
Splunk Employee
Splunk Employee

Hi,

I have a simple AWS environment, and want to create an EC2 instance with the Splunk SOAR (On-premises) AMI from the Amazon Marketplace running on it.

I am following these instructions from the Splunk Docs.

The issue I am facing is that when I attempt to log in to the deployed SOAR instance (after giving it 20 mins to initialise), I receive an DNS error as shown on the screenshot below. I am using the public IP address from the AWS console.

Screenshot 2022-11-04 at 11.16.31.png

Has someone an idea? Thanks in advance for your help and support!

 

Labels (1)
0 Karma
1 Solution

sschimper
Splunk Employee
Splunk Employee

I fixed the issue. I was connecting to the web interface via HTTP and it should have been HTTPS. I guess, I automatically assumed it would be the same as with the Splunk Enterprise AMI, since it doesn't have HTTPS enabled by default.

View solution in original post

0 Karma

sschimper
Splunk Employee
Splunk Employee

I fixed the issue. I was connecting to the web interface via HTTP and it should have been HTTPS. I guess, I automatically assumed it would be the same as with the Splunk Enterprise AMI, since it doesn't have HTTPS enabled by default.

0 Karma
Get Updates on the Splunk Community!

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...