# Restore from found-snapshots across clusters

**URL:** <https://discuss.elastic.co/t/restore-from-found-snapshots-across-clusters/353903>\
**Category:** Kibana\
**Tags:** snapshot-and-restore\
**Created:** [February 22, 2024, 5:11pm UTC](https://discuss.elastic.co/t/restore-from-found-snapshots-across-clusters/353903 "2024-02-22T17:11:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dan-cbm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan-cbm/32/125976_2.png) [@dan-cbm](https://discuss.elastic.co/u/dan-cbm)\
**Post date:** [February 22, 2024, 5:11pm UTC](https://discuss.elastic.co/t/restore-from-found-snapshots-across-clusters/353903/1 "2024-02-22T17:11:13Z")

</div>

Is it possible to use the default "found-snapshots" S3 repository to restore from one cluster into another (e.g. prod -\> test)? For context I'm using elastic cloud to host our deployment environments (managed on top of aws by elastic cloud).

From what I gather from the docs, I can add the prod environment snapshot repo as a read only snapshot repo inside of test's kibana and then do a restore.

However I ran into some IAM access issues when I tried to do this through the UI (using the "found-snapshots" configuration shown on prod). I will continue to troubleshoot this...

Another question, I see [from these docs](https://www.elastic.co/guide/en/cloud/current/ec-restore-snapshots-into-existing-deployment.html) you can apparently accomplish what I'm looking to do through [cloud.elastic.co](http://cloud.elastic.co) itself (rather than kibana). I initiated a restore this way from prod -\> test, but in test's kibana the "Restore Status" tab on the "snapshot and restore" page (e.g. `/app/management/data/snapshot_restore/snapshots`) is empty, so how are restore initiated through [cloud.elastic.co](http://cloud.elastic.co) related to those done in kibana?

I do see that a new snapshot repo ("\_clone\_80ce1d7f") now appears in test's kibana which I imagine is a complete clone of the snapshot repo in prod? But ultimately I want to connect the same repo as read only for convenient restores that I will schedule on recurring intervals.

Sorry for the disorganized braindump, I'd appreciate any insights, tips, or useful links. I've poured over the snapshot and restore docs already for some time but still find them somewhat sparse on the details I need.

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [February 24, 2024, 1:10am UTC](https://discuss.elastic.co/t/restore-from-found-snapshots-across-clusters/353903/2 "2024-02-24T01:10:46Z")

</div>

Most of these snapshost\_restore operations would be better to be done via the cloud UI since they require a few more sensitive operation when restoring system indices. For regular data you will have to check on what the errors and requirements are: for example I regularly use GCP snapshots for my test environment and the identity management is done via a json file that you configure and download from the GCS side.

---

<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:** [March 23, 2024, 1:11am UTC](https://discuss.elastic.co/t/restore-from-found-snapshots-across-clusters/353903/3 "2024-03-23T01:11:30Z")

</div>

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