Splunk Cloud cannot act as a Deployment Server for customer-owned Universal Forwarders or Heavy Forwarders. Customers must operate an on-premises (or customer-VPC) Deployment Server to distribute inputs.conf, props.conf, and splunkclouduf.spl across fleets using serverclass.conf.
In production environments, admins place the Deployment Server on a dedicated utility node or Heavy Forwarder, configure deploymentclient.conf on UFs to phone home on management port 8089, and run ./splunk reload deploy-server after updating server classes.
If you manage Splunk Enterprise 9.2+ forwarder nodes as your on-prem Deployment Server, note that manual UI client record deletion ("Delete Record" / DELETE /services/deployment/server/clients/<guid>) was deprecated; decommissioned clients age out automatically or are disabled locally via splunk disable deploy-client.
[serverClass:linux_web_ufs]
whitelist.0 = web-*.corp.example
[serverClass:linux_web_ufs:app:100_mycloudstack_splunkcloud]
restartSplunkd = true
[serverClass:linux_web_ufs:app:org_linux_inputs]
restartSplunkd = true