- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are Smartstore buckets uploaded to S3 immutable? We've been using Smartstore for almost a year and I have never seen an update to a bucket after its original upload to S3. Can anyone confirm this?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


Just like warm and cold on-prem buckets, S2 buckets never change.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The whole S3 SmartStore bucket is not immutable. At least in my instance anyway.
The actual index data, tsidx files, and other metadata files subtending the 'db' folder are immutable.
However, data model acceleration files located under the 'dma' folder do get updated/deleted as a normal part of Splunk operation.
Do we have something misconfigured here? Or, is what am what I am saying normal?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


That's normal and is just like on-prem.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


Just like warm and cold on-prem buckets, S2 buckets never change.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I am learning with Write-Once-Read-Many (WORM), there are situations where the buckets/tsidx files are re-uploaded when the indexers have hiccups during an upload.
https://community.splunk.com/t5/Deployment-Architecture/smartstore-splunk-smartstore-and-Data-integr...
