# Restore elastic search 5.5 snapshot in another aws account vpc cluster

**URL:** <https://discuss.elastic.co/t/restore-elastic-search-5-5-snapshot-in-another-aws-account-vpc-cluster/268101>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [March 23, 2021, 1:41pm UTC](https://discuss.elastic.co/t/restore-elastic-search-5-5-snapshot-in-another-aws-account-vpc-cluster/268101 "2021-03-23T13:41:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![swapna](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@swapna](https://discuss.elastic.co/u/swapna)\
**Post date:** [March 23, 2021, 1:41pm UTC](https://discuss.elastic.co/t/restore-elastic-search-5-5-snapshot-in-another-aws-account-vpc-cluster/268101/1 "2021-03-23T13:41:45Z")

</div>

Elastic Search Snapshot and Restore from one account cluster to another account vpc cluster

I followed this document

> **[Restore data from an Amazon ES domain in another AWS account](https://aws.amazon.com/premiumsupport/knowledge-center/es-restore-data/)**

1. Created Role , User and S3 bucket
2. Updated and attached the policies
3. Setup in Postman  
a) Authorization – AWS Keys , Region and Service Name (es)  
b) Headers – Content-type to application/json  
c) Body – s3 bucket settings (from the above link)
4. Register
5. Snapshot creation

Restore in another vpc cluster

1. Created Role, User and S3 bucket
2. Updated the attached polices
3. Created one more request (restorerepo) and set the AWS Authorization, Headers , Body with s3 bucket settings
4. Register the bucket

I am getting the below message

The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details

I tried even with GET stats

[https://vpcescluster.es.amazonaws.com:9200/\_stats](https://vpcescluster.es.amazonaws.com:9200/_stats) with AWS Authorization – Throws the above messge

[https://vpcescluster.es.amazonaws.com:9200/\_stats](https://vpcescluster.es.amazonaws.com:9200/_stats) with No Authorization – I get the stats

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 23, 2021, 2:20pm UTC](https://discuss.elastic.co/t/restore-elastic-search-5-5-snapshot-in-another-aws-account-vpc-cluster/268101/2 "2021-03-23T14:20:17Z")

</div>

We can not offer support on the service you are using as it's not the official service we are running. AWS built his own service with some subset of the features we have. You should ask their support.

BTW did you look at [Cloud by Elastic](https://www.elastic.co/cloud), also available if needed from [AWS Marketplace](https://aws.amazon.com/marketplace/pp/Elasticsearch-Inc-Elasticsearch-Service-on-Elastic/B01N6YCISK), [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure?tab=Overview) and [Google Cloud Marketplace](https://console.cloud.google.com/marketplace/details/endpoints/elasticsearch-service.gcpmarketplace.elastic.co)?

Cloud by elastic is one way to have access to **all features** , all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, Maps UI, Alerting and built-in solutions named [Observability](https://www.elastic.co/observability), [Security](https://www.elastic.co/security), [Enterprise Search](https://www.elastic.co/enterprise-search) and what is coming next 🙂 ...

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 23, 2021, 11:47pm UTC](https://discuss.elastic.co/t/restore-elastic-search-5-5-snapshot-in-another-aws-account-vpc-cluster/268101/3 "2021-03-23T23:47:17Z")

</div>

Welcome to our community! 😃

Please also note that 5.5 is [EOL](https://www.elastic.co/support/eol), it's _really_ **really** old and you should upgrade as a matter of urgency.

---

<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:** [April 20, 2021, 11:47pm UTC](https://discuss.elastic.co/t/restore-elastic-search-5-5-snapshot-in-another-aws-account-vpc-cluster/268101/4 "2021-04-20T23:47:53Z")

</div>

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