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

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...