⛏️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 Access Bastion • Room 1

Self-Service App Install (SSAI) & AppInspect Vetting

Splunk Cloud installs public Splunkbase apps and custom private apps through Self-Service App Install (SSAI) in Splunk Web or via the ACS API (apps/victoria on Victoria stacks, apps on Classic stacks). Every private package undergoes automated AppInspect vetting before deployment.

AppInspect validates packages against Cloud tag profiles such as cloud, private-app, private_victoria, or private_classic. Common vetting failures include packaging a /local/ directory or metadata/local.meta file, embedding plaintext passwords or secrets in .conf or Python files, invoking unsafe OS shell/filesystem commands, or failing Python 3 / python.version compatibility checks.

Remember two key Cloud nuances: installing restricted Splunkbase apps requires valid Splunk.com credentials and license acknowledgment (--acs-licensing-ack), and on Victoria Experience stacks, you cannot download previously uploaded apps back out of the Splunk Web UI.

Install Splunkbase and private apps via ACS CLI
acs apps install splunkbase \
  --splunkbase-id 742 \
  --acs-licensing-ack https://www.splunk.com/en_us/legal/splunk-general-terms.html

acs apps install private \
  --acs-legal-ack Y \
  --app-package ./my_custom_ta-1.2.0.tar.gz
Run splunk-appinspect inspect --included-tags cloud --included-tags private_victoria locally in CI/CD before uploading a private .tar.gz to ACS.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
❤️❤️❤️
Question 1 of 2
Which packaging mistake causes automated AppInspect vetting to reject a private app for Splunk Cloud?
AIncluding a /local/ directory, metadata/local.meta, or plaintext secrets inside the archive
BPlacing all default configurations and stanza definitions cleanly inside default/props.conf
CSetting python.version = python3 in commands.conf for custom Python 3 search command scripts
DAcknowledging the --acs-legal-ack Y flag during private application installation via ACS CLI