Splunk Cloud deployments vary by scale and compliance tier, including Single-Instance Cloud stacks for smaller workloads and Clustered stacks with dedicated Search Heads or a Search Head Cluster (SHC) paired with multi-AZ SmartStore indexers.
SmartStore separates compute from durable storage by keeping warm bucket metadata and active cache on local indexer NVMe/SSD volumes while storing authoritative bucket data in cloud object storage (Amazon S3 or Google Cloud Storage).
Deployment shape directly affects available self-service capabilities. For example, certain ACS limits.conf tuning endpoints require a distributed Search Head or SHC topology on Victoria rather than a single-instance stack, and Federated Search for Amazon S3 requires an AWS-hosted stack with a standalone Search Head or SHC.
On-Prem UFs/HFs --(TCP 9997 TLS)--> NLB --> SmartStore Indexers (S3/GCS)
API / Webhook Producers --(HTTPS 443)--> HEC Endpoint --> SmartStore Indexers
Analysts / Admins --(HTTPS 443)--> Load Balancer --> Search Head / SHC