Splunk Dev

Need Splunk Cloud Indexer URL to Allow in Firewall

schua
New Member

Hello,

I am new to Splunk Cloud and trying to configure Splunk Forwarder on one of the Linux boxes.

Here are the steps I did:
1. From the Splunk Cloud App-> Universal Forwarder, I downloaded and installed Universal Forwarder in the Linux box.
2. Downloaded and installed Universal Forwarder credentials successfully
3. restarted Splunk

My issue now is I have give instructions to my Network team to open port 9997 to Splunk Cloud indexer but I don't know where to get the URL(destination) of the indexer. Unlike Splunk Enterprise where you know the IP address of the server and put it in output.conf (server = serverIP:Port), I'm not sure where to get the URL.

Regards,
Sherwin

Tags (1)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi @schua,
if you have to perform a test with one target server you need to open only port 9997 to Splunk Cloud public URL not to the Indexer's IP address.
You can use the same method to connect to Splunk Cloud as you would with an on premises version: you just need to use the global dns name for your stack that you can find in your Cloud instance main page.

But anyway, if you have more targets to monitor I suggest to use a more structured architecture, adding one or two (better to have HA features) Heavy Forwarder/s to use as log concentrator/s.
In this way you have to open firewall routes only from this/these server to Splunk Cloud and not from all the targets.

Ciao.
Giuseppe

View solution in original post

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @schua,
if you have to perform a test with one target server you need to open only port 9997 to Splunk Cloud public URL not to the Indexer's IP address.
You can use the same method to connect to Splunk Cloud as you would with an on premises version: you just need to use the global dns name for your stack that you can find in your Cloud instance main page.

But anyway, if you have more targets to monitor I suggest to use a more structured architecture, adding one or two (better to have HA features) Heavy Forwarder/s to use as log concentrator/s.
In this way you have to open firewall routes only from this/these server to Splunk Cloud and not from all the targets.

Ciao.
Giuseppe

0 Karma
Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...