Will the Splunk Cloud REST API interface URI be different than On-Premise Splunk Enterprise?

[jlockD3]

Hi, we are thinking of switching from an existing on-premise Splunk Enterprise to Splunk Cloud.

Our concern is that we have an analytic/reporting app that searches and queries Splunk server via the API/Management port TCP 8089 (Our local on-premise Splunk Server will have an URI like 192.168.1.2:8089). If we switch to Splunk Cloud, will the server URI and port become dynamic since the instance is on the cloud? If so, our analytic app is unable to handle dynamic URI and port.

This might influence our decision to purchase Splunk Cloud or not.

[ussina04]

Hi,

Splunk Cloud API url will be different but 8089 will only be used to access the API like below:

Use the following URL for single-instance managed deployments.
https://.cloud.splunk.com:8089

Use the following URL for clustered deployments. If necessary, submit a support case to open port 8089 on your deployment.
https://.splunkcloud.com:8089

Self-service Splunk Cloud deployments
https://input-.cloud.splunk.com:8089

Also there are limitations on using Cloud API, you can not do :

Modifying configuration of deployment servers and client configurations and distributed components (indexers, search heads, clustering)
Restarting a Splunk Cloud deployment
Executing debug commands
Installing apps and modifying app configurations

rest searches and queries can be run via cloud API of Splunk.