Federated Search allows a Splunk Cloud search head to query remote Splunk Cloud or Splunk Enterprise deployments (or DDSS/Amazon S3 datasets) without re-ingesting raw logs. Access is governed by two authorize.conf capabilities: fsh_search (to execute federated searches) and fsh_manage (to configure providers and federated indexes).
In Standard mode, admins define both a federated provider (pointing to the remote deployment with a remote service account) and explicit federated indexes mapping remote indexes, saved searches, or data models. Users query them explicitly using index=federated:<fed_index> or | from federated:<dataset>, executing on the remote side under the provider service account.
In Transparent mode—built for hybrid-search migration—you define only the federated provider without per-index federated index mappings. Users run standard SPL (such as sourcetype=access_*) using their local permissions, and Splunk injects a splunk_federated_provider field into results. Remember to open outbound port 8089 via ACS (access/outbound-ports) and allowlist the Cloud search head IP on the remote target.
# Standard mode (explicit federated index or dataset)
index=federated:remote_sec_events action=failure | stats count by src_ip
| from federated:remote_dm | timechart span=5m count by host
# Transparent mode (no federated: prefix; adds splunk_federated_provider)
sourcetype=access_combined status>=500 | stats count by splunk_federated_provider, host