⛏️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 1

ACS API v2 & CLI Authentication

The Admin Config Service (ACS) API v2 and companion acs CLI enable Splunk Cloud administrators to automate stack configuration without filing Support tickets. All commercial stacks expose the API at https://admin.splunk.com/{stack}/adminconfig/v2/, while FedRAMP IL2 stacks use https://admin.splunkcloudgc.com/{stack}/adminconfig/v2/.

Every ACS call requires a Bearer JSON Web Token (JWT) issued for a user holding the sc_admin role. You generate authentication tokens in Splunk Web under Settings > Tokens or via the /tokens endpoint, then authenticate the CLI using acs config add-stack and acs login (or acs setup).

Keeping the acs CLI up to date matters in production: bulk operations require CLI v2.5.0 or newer, and DDSS self-storage-locations commands require CLI v2.9.0 or newer.

Configure ACS CLI and check stack status
acs config add-stack mycloudstack
acs config use-stack mycloudstack
acs login
acs status current-stack
Always rotate and scope JWT auth tokens carefully because any token tied to an sc_admin user can mutate Cloud indexes, HEC tokens, and IP allowlists.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Complete the ACS API v2 endpoint and authentication details.
Commercial Splunk Cloud stacks expose ACS API v2 at https:///{stack}//v2/, authenticated with an Authorization: <JWT> header issued to a user with the role.