Once active searchable retention (DDAS / searchableDays) expires, Splunk Cloud offers two long-term archiving models: Dynamic Data Active Archive (DDAA) and Dynamic Data Self Storage (DDSS). Both are mutually exclusive per index.
DDAA is a Splunk-managed cloud archive. Admins can restore archived date ranges directly through the Splunk Web UI (typically becoming searchable within 24 hours). Restored DDAA data remains active for 30 days before auto-expiring, and total restored data is capped at an entitlement limit (typically 10% of DDAS active searchable storage, or up to 20% on expanded enterprise tiers).
DDSS exports rolled buckets to a customer-owned AWS S3 or Google Cloud Storage bucket in the same region, configured via an ACS-generated IAM policy (GET .../buckets/{bucketName}/policy), optional KMS CMK permissions (kms:Decrypt, kms:GenerateDataKey*, kms:DescribeKey), and acs self-storage-locations create. DDSS has no 1-click UI restore back into the main Cloud stack—you query DDSS buckets via Federated Search for DDSS or restore buckets into a separate Splunk Enterprise instance.
# 1. Retrieve the IAM bucket policy via ACS API v2 before creation
curl -s -H "Authorization: Bearer $ACS_TOKEN" \
"https://admin.splunk.com/$STACK/adminconfig/v2/cloud-resources/self-storage-locations/buckets/corp-splunk-ddss/policy"
# 2. Apply policy in AWS/GCP, register location, inspect, and create index
acs self-storage-locations create --bucket-name corp-splunk-ddss --title "Corp DDSS"
acs self-storage-locations list
acs indexes create --name compliance_logs --searchable-days 90 \
--self-storage-bucket-path s3://corp-splunk-ddss/compliance