Splunk Search

What is the purpose of our Splunk instance phoning home to an external IP over port 443?

jbsplunk
Splunk Employee
Splunk Employee

We've noticed that our splunk server was phoning home to an external IP over port 443.  What's the purpose of this traffic?

Tags (3)

jreuter_splunk
Splunk Employee
Splunk Employee

This is most likely splunk phoning home to apps.splunk.com to check for updates. You can verifiy if this is the case by looking up the destination IP:

dig +short apps.splunk.com
54.187.11.200

dig +short -x 54.187.11.200
ec2-54-187-11-200.us-west-2.compute.amazonaws.com.

You should see a correlating event in the splunkd.log, but I believe only if there is an error:

WARN  HTTPClient - Connect to=apps.splunk.com:443 timed out; exceeded 10sec
ERROR ApplicationUpdater - Error checking for update, URL=/api/apps:resolve/checkforupgrade: Connect to=https://apps.splunk.com timed out; exceeded 10sec
ERROR HTTPClient - Cannot resolve IP of host=apps.splunk.com: No such host is known.

If you would like to disable this behavior, check this answer:
http://answers.splunk.com/answers/28616/how-can-automatic-update-checking-be-disabled-for-splunkbase...

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...