Getting Data In

Pull syslog data from EC2 instance into Splunk

olgamirth
New Member

We're running an on-prem instance of Splunk Enterprise behind a firewall which (currently) does not permit ingress on ports 9996 or 9997. As such, I can't get EC2 syslog data in using the UF. Is it possible to get our on-prem instance of Splunk to pull the syslog data, in something close to real-time, from the EC2 instance. Is there a better way to architect this or should I just resign myself to do battle with our network administrators?

Thanks,
Mike

0 Karma
1 Solution

jplumsdaine22
Influencer

If they will only let you communicate TO AWS, then run an indexer in AWS, and peer your on prem search head with the AWS indexer.

View solution in original post

0 Karma

jplumsdaine22
Influencer

If they will only let you communicate TO AWS, then run an indexer in AWS, and peer your on prem search head with the AWS indexer.

0 Karma

olgamirth
New Member

Oh, hey! I didn't think of that. Thanks!

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...