Selecting the right ingestion tier depends on both your Splunk Cloud experience and the data source type. In Classic Experience, cloud-hosted API polling and scripted inputs run on the Inputs Data Manager (IDM), whereas Victoria Experience removes the IDM and runs those modular inputs directly on the Search Head tier.
Customer-managed Heavy Forwarders (HFs) remain essential whenever you need on-premises network listeners (such as syslog via SC4S or TCP/UDP inputs), Splunk DB Connect against private databases, or heavy pre-ingest filtering and masking before traffic leaves your network.
For cloud-native telemetry from AWS, Azure, or GCP, Splunk Data Manager provides a guided, zero-forwarder automation workflow that provisions cloud-provider pipelines (such as Kinesis Firehose, Event Hubs, or Pub/Sub) into Splunk Cloud HEC.
# File/Windows logs on endpoints -> Universal Forwarder + splunkclouduf.spl
# Private DB Connect / Syslog / Local Masking -> On-prem Heavy Forwarder
# Cloud SaaS / API polling -> Victoria Search Tier (or Classic IDM)
# Native AWS/Azure/GCP account telemetry -> Splunk Data Manager (HEC)