Splunk Cloud Self Storage (DDSS) Direct Access
Bring your Splunk data straight into Cribl Lake, bypassing Cribl Stream processing.
You can use the Splunk Cloud Self Storage option to archive one or more Splunk Cloud indexes directly to Cribl Lake. This option bypasses routing or processing it through Cribl Stream. Once your data is integrated with Cribl Lake, Cribl Stream and Cribl Search can access it as a Lake Dataset.
Requirements for Splunk Cloud Direct Access
To set up this integration, you need a Splunk index (new or existing).
You can configure one Splunk Cloud Direct Access Source per Workspace.
See other Limitations later in this topic.
Configure Splunk Cloud Direct Access
To configure this integration, you’ll work back and forth between Splunk Cloud and Cribl Lake to share linking identifiers. The major steps are:
- In Splunk Cloud, get your Splunk Cloud ID.
- In Cribl Lake, create a Cribl Lake Source.
- In Splunk Cloud, connect your Cribl Lake bucket.
- In Cribl Lake, provision your Lake.
- In Splunk Cloud, test and submit the connection.
- In Cribl Lake, create a Cribl Lake Dataset.
Get Your Splunk Cloud ID
You’ll need to find and copy your Splunk Cloud ID, which is the first part of your Splunk Cloud URL and the 12-character S3 bucket string.
For example, if you administer Splunk Cloud Platform for Hungry Goats Computing, and
your Splunk Cloud URL is hungrygoatscomputing.splunkcloud.com, then your Splunk Cloud ID is
hungrygoatscomputing-{12-character s3 string}.
You can retrieve the AWS bucket prefix using one of the following methods:
Use the Splunk Cloud Platform Admin Config Service (ACS) API to manage DDSS self storage locations programmatically. For endpoint and payload details, see the Splunk docs on how to manage DDSS self storage locations in their Admin Config Service manual.
In Splunk Cloud Platform, start the workflow to configure an Amazon S3 self storage location. Splunk shows the required bucket name prefix in the Amazon S3 bucket name field (your Splunk Cloud ID plus the Splunk character string, which you enter before the rest of the bucket name). For the full UI steps, search for the Splunk doc topic on how to store expired Splunk Cloud Platform data.
Create Cribl Lake Source
In Cribl Lake, create the integration with your Splunk Cloud instance:
- From the sidebar, select Direct Access.
- Select the Splunk Cloud Self Storage Source, and select Next.
- In the Splunk Cloud ID field, paste your ID that you copied from Splunk Cloud in the previous section.
- Optionally, enter a Description of this Lake integration’s purpose.
- From the Region drop-down, select the AWS Region of your Splunk Cloud Platform.
- Select Next.
- Copy the Cribl Lake bucket name to your clipboard for the next section.

Connect Splunk Cloud to Your Cribl Lake Storage Location
Next, return to your Splunk Cloud Platform, to point this environment to the Storage Location you’ve created in Cribl Lake:
- In the Amazon S3 bucket name field, paste Cribl Lake bucket name you copied in the previous section.
- Select Generate to generate a bucket policy.
- Copy the resulting bucket policy to your clipboard for the next section.
Provision Your Lake
Return to Cribl Lake to link your bucket policy and provision the new Lake:
- In the AWS S3 bucket policy pane, paste the Splunk Cloud bucket policy you copied in the previous section.
- Select Save.
- Wait a few minutes for your new Lake to be provisioned.
Cribl provisions the underlying object storage for you during this step. Cribl-managed Lake storage is encrypted at rest by default.

Test and Submit the Connection
After provisioning is complete in Cribl Lake, test the connection from Splunk Cloud:
- In the Self Storage Locations dialog, select Test.
Splunk Cloud will write a 0 KB test file to verify that Splunk Cloud Platform has permissions to write to Cribl Lake.
- If you see a success message, select Submit to finish linking your Self Storage location to Cribl Lake.
- If the test fails, see Troubleshooting Direct Access.
Create Cribl Lake Dataset
Once you’ve verified the connection from Splunk Cloud, your final setup step is to create a Lake Dataset to contain your data. Each Splunk index maps to a single Lake Dataset, and no additional Search dataset setup is required. Follow the steps in Create a New Lake Dataset, being careful to add these specific requirements to handle DDSS data:
- Give the Dataset an ID that exactly matches your Splunk index name from Set Up Splunk Self Storage Location. (Otherwise, you will be unable to search or replay your data.)
- Set the Storage Location to the Splunk Cloud Self Storage (DDSS) location. Cribl Lake automatically sets the Dataset format to DDSS and hides Data format.
Save your new Dataset, and your Splunk data should begin flowing into it. That’s it!
Search Your DDSS Data
Because you gave the Lake Dataset the same ID as your Splunk index, naming the Dataset in a query also names the index. Cribl Search scopes the search to that index for you, so you don’t need an index filter in the query:
dataset="my_index" earliest=-7d latest=-1dTo search several archived indexes at once, combine the Datasets, as in
dataset="my_index" or dataset="my_other_index", or match them with a wildcard, as in dataset="my_*".
This differs from a Cribl Search federated Dataset that points at a Splunk self-storage bucket of your own, where one Bucket path covers every index. On those Datasets, name the index in the query. See Amazon S3 Partitioning Schemes.
For the Datatype that parses the journal files, see Dataset Type v2 and DDSS.
Detach a Splunk Cloud Source
Delete a Splunk Cloud Self Storage Source when you no longer want Splunk Cloud to write to its Cribl Lake bucket. Deleting the Source detaches it from its Storage Location. Cribl Lake retains the Storage Location, bucket, Datasets, and data. Existing Datasets remain editable and searchable.
To detach the Source:
- From the Cribl Lake sidebar, select Direct Access.
- Open the Splunk Cloud Self Storage Source.
- Select Delete, then confirm the deletion.
Cribl Lake starts revoking Splunk Cloud access in the background. The Source disappears from Direct Access, and its Storage Location remains on the Storage Locations page with the Detached status.
You can’t attach new DDSS Datasets to a detached Storage Location. You also can’t create another Splunk Cloud Self Storage Source while the detached Storage Location exists.
Permanently Delete the Storage Location and Data
Deleting a detached Storage Location permanently deletes its bucket and data. To delete it:
- Delete every Dataset connected to the Storage Location.
- Wait for Dataset(s) to finish deleting.
- From the sidebar, select Storage Locations, then open the detached Storage Location.
- Select Delete, then confirm the deletion.
Cribl Lake blocks you from deleting a Storage Location while any Dataset remains connected.
Other Ways to Break the Connection
- In Splunk Cloud, deleting a Self Storage location that’s linked to a Cribl Lake Dataset means that Splunk Cloud will no longer archive data to Cribl Lake. This deletion does not affect data already stored within Cribl Lake.
- If you cancel your Splunk Cloud account, your Splunk Cloud Self Storage Source in Cribl Lake can remain intact. Cribl Stream Collectors and Cribl Search queries can continue reading the current Dataset contents, but Splunk Cloud can’t write new data to the Dataset.
Limitations of Splunk Cloud Direct Access
A Lake Dataset created and populated via Splunk Cloud Direct Access is read-only to other Cribl products. So, although both Cribl Stream and Cribl Search can process data from the Dataset, neither product can write to it.
A Lake Dataset populated through Splunk Cloud Direct Access must use the Splunk Cloud Self Storage (DDSS)
Storage Location, not the default Cribl Lake location or an external bucket.
To ingest data directly into a Cribl Search lakehouse engine, see Get Data In in Cribl Search.
For Cribl-managed storage, retention is enforced at the Dataset level only.
Troubleshooting Direct Access
If Splunk Cloud fails to write the test file to your Lake Dataset, look for the following possible sources of error. Correcting each of these requires re-creating your integration from scratch:
- Regions mismatched between Splunk Cloud and Cribl.Cloud.
- Bucket name does not start with the Splunk Cloud ID.
- Amazon S3 bucket policy not pasted in accurately.