All Apps and Add-ons

Accessing Splunk Web installed on EC2 instance from Internet

koshyk
Super Champion

I have installed Splunk Enterprise in AWS for test purposes (Splunk 6.2x) . Installation was smooth and internal access working perfectly.
Though Splunk put forward internal address while it started ("http://ip-172-31-40-50:8000") , i have tried accessing it using external IP (eg 54.152.7.160)
External Access didn't work http://54.152.7.161:8000/

I have tried changing VPC entries, Network Inbound Traffic to allow 8000 from any source (in Default as well as in custom rule)

But still it is not working.
ANy idea how to get Splunk working externally in AWS?

Cheers

Tags (2)
1 Solution

koshyk
Super Champion

Found the issue. The issue was because I didn't enable "Security Group" settings. in https://console.aws.amazon.com/ec2/v2/home

So inorder to access Custom Port externally..

Security Groups -> Create (or modify) security group -> Inbound

Type= Custom,Protocol=TCP,Port=8000 , Source=0.0.0.0/0

View solution in original post

koshyk
Super Champion

Found the issue. The issue was because I didn't enable "Security Group" settings. in https://console.aws.amazon.com/ec2/v2/home

So inorder to access Custom Port externally..

Security Groups -> Create (or modify) security group -> Inbound

Type= Custom,Protocol=TCP,Port=8000 , Source=0.0.0.0/0

panache
New Member

Thank you for your help

0 Karma
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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...