Admin Config Service (ACS) requirements and compatibility matrix

This page lists basic requirements and compatibility information for the Admin Config Service (ACS) API.

To get started using the ACS API, see Basic setup and usage concepts for the Admin Config Service (ACS) API

Requirements

To use the ACS API with your Splunk Cloud Platform deployment:

FedRAMP IL2 requirements

ACS is supported on all FedRAMP IL2-compliant versions of Splunk Cloud Platform.

To run ACS API operations on FedRAMP IL2, you must specify the ACS FedRAMP IL2 server URL https://admin.splunkcloudgc.com in the API request, instead of the default ACS server URL https://admin.splunk.com. For example:

JSON
curl 'https://admin.splunkcloudgc.com/{stack_name}/adminconfig/v2/indexes' \
--header 'Authorization: Bearer eyJraWQiOiJzcGx1bmsuc2VjcmV0Iiwi…'
Note: FedRAMP IL2 deployments do not support ACS authentication token (tokens) endpoint operations. FedRAMP IL2 deployments do not support the ACS CLI setup and login commands, which use the ACS tokens endpoint to generate authentication tokens.
Note: FedRAMP IL2 deployments do not support editing limits.conf using the Configure Limits UI in Splunk Web.

For more information on Splunk platform support for FedRAMP, see Compliance at Splunk.

FedRAMP High requirements

ACS is supported on all FedRAMP High-compliant versions of Splunk Cloud Platform (10.1.2507 and higher).

To run ACS API operations on FedRAMP High, you must specify the ACS FedRAMP High server URL https://admin.splunkcloudfed.com in the API request, instead of the default ACS server URL https://admin.splunk.com. For example:

JSON
curl 'https://admin.splunkcloudfed.com/{stack_name}/adminconfig/v2/indexes' \
--header 'Authorization: Bearer eyJraWQiOiJzcGx1bmsuc2VjcmV0Iiwi…'
Note: Splunk Cloud Platform supports FedRAMP High on Classic Experience only.
Note: FedRAMP High deployments do not support ACS authentication token (tokens) endpoint operations. FedRAMP High deployments do not support the ACS CLI setup and login commands, which use the ACS tokens endpoint to generate authentication tokens.
Note: FedRAMP High deployments do not support viewing Maintenance Windows through the Cloud Monitoring Console (CMC) UI in Splunk Web.
Note: FedRAMP High deployments do not support editing limits.conf using the Configure Limits UI in Splunk Web.

ACS compatibility matrix

The table shows compatibility for ACS-supported features on Victoria Experience and Classic Experience.

ACS-supported feature Victoria Experience Classic Experience
App permissions Yes No
Authentication tokens Yes Yes
Export apps Yes No
HEC tokens Yes Yes
Indexes Yes Yes
IP allow lists Yes Yes
limits.conf configuration Yes No
Maintenance windows Yes Yes
Outbound ports Yes Yes
Private apps Yes Yes *
Private connectivity Yes Yes
Restarts Yes Yes
Splunkbase apps Yes Yes *
Users, roles, and capabilities Yes Yes
ACS CLI Yes Yes **
FedRAMP IL2 Yes Yes
FedRAMP High No Yes
Terraform Provider for ACS Yes Yes
Note: *Classic Experience supports ACS app management on all search heads except premium search heads.
Note: **Classic Experience supports ACS CLI bulk operations for HEC tokens and indexes only.

Determine your Splunk Cloud Platform Experience

Each Splunk Cloud Platform stack has an Experience designation: Classic or Victoria. Some ACS features are compatible with Victoria Experience only, while others, such as private app management, provide different endpoints for Classic Experience and Victoria Experience.

To find your Splunk Cloud Platform Experience:

  1. In Splunk Web, click Support & Services > About.
  2. In the About panel, under Splunk Cloud, find your Experience: Classic or Victoria.

After you determine your Splunk Cloud Platform Experience, use the ACS feature endpoints that apply to your Experience.

For more information on Splunk Cloud Platform Experience, see Determine your Splunk Cloud Platform Experience in the Splunk Cloud Platform Admin Manual.