# Searchable Snapshot - S3 - Object Lock

**URL:** <https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [December 15, 2023, 6:44am UTC](https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418 "2023-12-15T06:44:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![digital-thought](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@digital-thought](https://discuss.elastic.co/u/digital-thought)\
**Post date:** [December 15, 2023, 6:44am UTC](https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418/1 "2023-12-15T06:44:11Z")

</div>

I have implemented a Frozen Tier with Searchable Snapshots within AWS S3.  
To further protect the data and prevent deletion, I am looking to setup "Object Lock".

Will the use of "Object Lock" interfere in anyway with Elastic's Searchable Snapshot process?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 15, 2023, 9:46am UTC](https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418/2 "2023-12-15T09:46:51Z")

</div>

Yes, that'll interfere with the snapshotting process. It won't be fatal, but I expect you'll see a lot of errors in the logs. Moreover it won't actually ensure that the data in the snapshots remains accessible to Elasticsearch, because accessibility is determined by the repository metadata which is written to new blobs on each change so locking old blobs won't help.

---

<div class="post-metadata">

**Author:** ![digital-thought](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@digital-thought](https://discuss.elastic.co/u/digital-thought)\
**Post date:** [December 15, 2023, 10:01am UTC](https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418/3 "2023-12-15T10:01:42Z")

</div>

Thanks David.

What would be a good approach to perform backups snapshots? I was looking at lifecycle policies on the s3 to push data to another bucket.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 15, 2023, 10:45am UTC](https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418/4 "2023-12-15T10:45:22Z")

</div>

See these docs:

> **[Register a snapshot repository | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#snapshots-repository-backup)**

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 12, 2024, 10:45am UTC](https://discuss.elastic.co/t/searchable-snapshot-s3-object-lock/349418/5 "2024-01-12T10:45:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.