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.
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