# Migrate cloud.elastic.co index from amazon deployment to azure deployment

**URL:** <https://discuss.elastic.co/t/migrate-cloud-elastic-co-index-from-amazon-deployment-to-azure-deployment/216302>\
**Category:** Elasticsearch\
**Created:** [January 23, 2020, 5:23pm UTC](https://discuss.elastic.co/t/migrate-cloud-elastic-co-index-from-amazon-deployment-to-azure-deployment/216302 "2020-01-23T17:23:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vchalmel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vchalmel/32/11681_2.png) [@vchalmel](https://discuss.elastic.co/u/vchalmel)\
**Post date:** [January 23, 2020, 5:23pm UTC](https://discuss.elastic.co/t/migrate-cloud-elastic-co-index-from-amazon-deployment-to-azure-deployment/216302/1 "2020-01-23T17:23:09Z")

</div>

Hi !

In order to avoid connexion stability issues for an Azure hosted API using an originally AWS hosted elastic cloud deployment I am seeking to migrate the indices of said deployment to a new Azure hosted deployment in the same azure region my API is running in.

Using the [cloud.elastic.co](http://cloud.elastic.co) GUI only allows snapshots transfers on same host solution and same region.

So trying to do it manually I can't find a way to either

1. add an azure storage repository for snapshots on the AWS hosted elastic deployment  
or
2. add an aws repository on the azure hosted new deployment to restore from.

I first tried to use [this way](https://www.elastic.co/guide/en/cloud/current/ec-migrate-data.html#ec-restore-snapshots) to add the s3 snapshot to the azure deployment but got an error telling me it couldn't reach the snapshot

I then tried to install the azure-repository plugin and PUT a "type":"azure" snapshot to the S3 deployment but got an error (repository type [azure] does not exist) so I guess those are not compatible.

Is there anyway to enable any solution to exchange snapshots between s3 and azure ?

Thanks.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 27, 2020, 10:48am UTC](https://discuss.elastic.co/t/migrate-cloud-elastic-co-index-from-amazon-deployment-to-azure-deployment/216302/2 "2020-01-27T10:48:21Z")

</div>

How about [reindex from remote](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/reindex-upgrade-remote.html) maybe?

---

<div class="post-metadata">

**Author:** ![vchalmel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vchalmel/32/11681_2.png) [@vchalmel](https://discuss.elastic.co/u/vchalmel)\
**Post date:** [January 30, 2020, 12:33pm UTC](https://discuss.elastic.co/t/migrate-cloud-elastic-co-index-from-amazon-deployment-to-azure-deployment/216302/3 "2020-01-30T12:33:46Z")

</div>

Much longer than a snapshot restoration, but a workaround anyway. 👌

---

<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:** [February 27, 2020, 12:46pm UTC](https://discuss.elastic.co/t/migrate-cloud-elastic-co-index-from-amazon-deployment-to-azure-deployment/216302/4 "2020-02-27T12:46:47Z")

</div>

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