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:

ACS compatibility matrix

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

ACS-supported feature Victoria Experience Classic Experience Notes
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 Classic Experience does not support app management on premium search heads.
Private connectivity Yes Yes
Restarts Yes Yes
Splunkbase apps Yes Yes Classic Experience does not support app management on premium search heads.
Users, roles, and capabilities Yes Yes
ACS CLI Yes Yes Classic Experience supports ACS CLI bulk operations for HEC tokens and indexes only.
FedRAMP IL2 Yes Yes
FedRAMP High No Yes
Terraform Provider for ACS Yes Yes

ACS requirements for compliance environments

Use the ACS API in a PCI DSS, HIPAA, FedRAMP IL2, or FedRAMP High Splunk Cloud Platform environment.

To use ACS in a PCI DSS, HIPAA, FedRAMP IL2, or FedRAMP High environment, specify the ACS endpoint URL for your environment in the API request. PCI DSS and HIPAA environments use the default ACS endpoint URL, https://admin.splunk.com. FedRAMP IL2 and FedRAMP High environments use their own URLs. For example, on FedRAMP IL2:

JSON
curl 'https://admin.splunkcloudgc.com/{stack_name}/adminconfig/v2/indexes' \
--header 'Authorization: Bearer eyJraWQiOiJzcGx1bmsuc2VjcmV0Iiwi…'

For the ACS endpoint URL and feature limitations for each environment, see ACS-supported compliance environments. For more information on Splunk platform support for FedRAMP, see Compliance at Splunk.

ACS-supported compliance environments

Find the ACS endpoint and feature limitations that apply to your commercial, FedRAMP, PCI DSS, or HIPAA Splunk Cloud Platform environment.

ACS supports all PCI DSS, HIPAA, FedRAMP IL2 (FedRAMP Moderate), and FedRAMP High Splunk Cloud Platform environments, on both Victoria Experience and Classic Experience. PCI DSS and HIPAA environments support the same ACS features as commercial environments. In all supported environments, you can use ACS to manage IP allow lists.

The following table lists IP allow list support, the ACS endpoint to specify in API requests, and feature limitations for each environment:

Environment IP allow lists ACS endpoint Notes
Commercial Yes https://admin.splunk.com
PCI DSS Yes https://admin.splunk.com Requires IP allow list rules to access PCI DSS environments.
HIPAA Yes https://admin.splunk.com Requires IP allow list rules to access HIPAA environments.
FedRAMP IL2 Yes https://admin.splunkcloudgc.com
  • Does not support the ACS authentication token (tokens) endpoint or the ACS CLI setup and login commands, which use the tokens endpoint.
  • Does not support editing limits.conf using the Configure Limits UI in Splunk Web.
  • Does not support viewing maintenance windows through the Cloud Monitoring Console (CMC) UI in Splunk Web (FedRAMP High only).
FedRAMP High Yes https://admin.splunkcloudfed.com

For examples and requirements for these environments, see ACS compliance environment requirements. For more information on supported compliance environments, see Splunk Cloud Platform Service Details.

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.