Getting Data In

My local Universal Forwarder to AWS Splunk Instance

tentontitan
New Member

I have a splunk instance running on Amazon AWS for testing. I'm trying to configure my home pc to forward (universal forwarder) to the AWS Splunk instance.

So far I'm not seeing anything. My AWS instance is on 1.2.3.4 (fake obviously). And my computers outputs.conf is:

[tcpout]
defaultGroup = group1

[tcpout:group1]
server = 1.2.3.4:9997

I'm not sure if there is anything else I should be doing. My router is allowing traffic on 9997. I can hit the web interface - 1.2.3.4:8000. I'm not sure what is happening.

0 Karma

gjanders
SplunkTrust
SplunkTrust

If you have setup the outputs.conf the _internal data should start going through, so you should be able to search the _internal index for the host sending the data.

Does telnet work to connect to port 9997 on the remote address?
I'm assuming the remote side is listening on port 9997...

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!

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

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 ...