User is unable to add more IP addresses to the Allow Management List

Available Languages

Updated:September 30, 2026

Document ID:SPLK050037

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Cloud

Description

According to Splunk documentation, AWS users have a limit of 230 IP addresses for allow listing. Therefore receiving an error when the user knows they haven't used up the entire limit can be confusing.
Allow listing error

Investigation

The AWS limits are divided into groups, the s2s falls under the indexer security group. The total limit for the combined indexer security group is 230 however for individual features within the subgroup the limit is 200

Indexer subgroup limit: 230
Feature 1 (s2s): 200
Feature 2 (HEC): 200

Basically, the feature should be <= 200 and the sum of all the features in a security group <= 230

Splunk documentation

The most important part of this documentation: "ACS enforces a hard limit of 200 IP subnets for each ACS feature allow list."

Resolution

The only available workaround is to consolidate the IPs in CIDR blocks to get past the 200 limit.

Revision History

Revision	Publish Date	Comments
1.0	30-Sep-2026	Initial Release

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

This Document Applies to These Products

Splunk Cloud