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!

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Cultivate Your Career Growth with Fresh Splunk Training

Growth doesn’t just happen—it’s nurtured. Like tending a garden, developing your Splunk skills takes the right ...