Security

Problems caused by Splunk web interface url

liny
Engager

I'm installing Splunk 4.3 on EC2 instance(Linux image) and want to access the Splunk web interface outside of EC2. The problem is every EC2 instance have two DNS, one is privete DNS and the other is public DNS. For example,
Public DNS:ec2-75-101-214-21.compute-1.amazonaws.com,
private DNS:ip-10-80-201-152.ec2.internal
After I start splunk, it says: The Splunk web interface is at http://ip-10-80-201-152:8000. Actually, this is neither public DNS nor private DNS. It is just a part of the private DNS!
How can get around this problem? Can I change the Splunk web interface url(DNS)?

Tags (2)
0 Karma

Linegod
Path Finder

Splunk attempts to determine the URL - but it doesn't enforce it anywhere. It is simply listening on port 8000 on your server.

You should be able to access it at http://your.public.address:8000

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...