Splunk Cloud protects stack surfaces through feature-specific IP allowlists managed via ACS under access/{feature}/ipallowlists (IPv4) and access/{feature}/ipallowlists-v6 (IPv6). Supported features include s2s (TCP 9997), hec (HTTPS 443), search-api (port 8089), search-ui (Splunk Web), and on Classic stacks, idm-api and idm-ui.
Each feature allowlist enforces a strict quota of 200 subnets per feature, and features sharing an architectural group (such as hec and s2s on the indexer tier) share a combined ceiling of 230 subnets. Overly broad or fragmented CIDR lists quickly hit these limits unless consolidated into clean CIDR blocks.
When Splunk Cloud needs to initiate outbound connections—such as Federated Search over port 8089 to an external Splunk Enterprise deployment or outbound webhook/alert integrations—you configure outbound firewall rules using access/outbound-ports or acs outbound-port create.
acs ip-allowlist create hec --subnets 203.0.113.0/24
acs ip-allowlist list s2s
acs outbound-port create 8089 --subnets 198.51.100.10/32