topic Re: Which instance should I send REST API to? in Splunk Enterprise

Which instance should I send REST API to?

chenyt — Mon, 17 Jan 2022 16:20:29 GMT

Hi, everyone.

I am new to Splunk. I have an environment with 3 nodes indexer cluster + cm + Search Head. I am wondering which instance I should send my request to when using REST API?

I have checked API reference and API User tutorial, try to figure it out which endpoint for which instance, but no luck. It seems all HTTPS request send to localhost:8089?

Please help. Thanks.

Re: Which instance should I send REST API to?

tscroggins — Mon, 17 Jan 2022 16:26:12 GMT

@chenyt

You should send REST API requests to your search head: https://yourhostname:8089. In most cases, REST API access to the your indexers should be limited to other Splunk instances. Your search head provides the authentication and authorization configuration necessary to control access to your data.

Re: Which instance should I send REST API to?

chenyt — Mon, 17 Jan 2022 16:54:05 GMT

@tscroggins

Thanks for the reply.

Does that mean I don't need to bother which endpoint for which instance, just configure the authentication and authorization on Search Head then send all the REST API request to it?

Re: Which instance should I send REST API to?

SinghK — Mon, 17 Jan 2022 17:01:16 GMT

Yes, because SH will do the rest and fetch the results of you query.

Re: Which instance should I send REST API to?

tscroggins — Mon, 17 Jan 2022 17:06:45 GMT

@chenyt

Yes, the configuration you define on the search head--users, roles, etc.--will be pushed to the indexers in a bundle used during the search. Different search heads can define different authentication and authorization settings.

Splunk security is decentralized. While you can and should define strict authorization settings on your indexers through configuration deployed by your cluster manager, your users should access the environment through the search head.

Re: Which instance should I send REST API to?

chenyt — Mon, 17 Jan 2022 17:11:59 GMT

@tscroggins @SinghK

Thank you very much.