⛏️GetSplunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
The Control Plane • Room 2

IP Allowlists & Outbound Ports

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.

Manage IP allowlists and outbound ports with ACS CLI
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
Consolidate individual /32 host entries into contiguous CIDR ranges before calling ACS so you stay well below the 200-per-feature and 230-shared subnet ceilings.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
❤️❤️❤️
Question 1 of 2
What are the maximum IP allowlist subnet quotas enforced by the ACS API?
A50 subnets per individual feature and 100 subnets across the stack
B500 subnets per individual feature with unlimited shared group subnets
C1,024 subnets for s2s forwarding and 64 subnets for hec ingestion
D200 subnets per feature and 230 subnets shared across a feature group