# S3 No Such Key when restoring snapshot in 5.x with base\_path

**URL:** <https://discuss.elastic.co/t/s3-no-such-key-when-restoring-snapshot-in-5-x-with-base-path/102006>\
**Category:** Elasticsearch\
**Created:** [September 27, 2017, 3:55pm UTC](https://discuss.elastic.co/t/s3-no-such-key-when-restoring-snapshot-in-5-x-with-base-path/102006 "2017-09-27T15:55:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pykler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pykler/32/22576_2.png) [@pykler](https://discuss.elastic.co/u/pykler)\
**Post date:** [September 27, 2017, 3:55pm UTC](https://discuss.elastic.co/t/s3-no-such-key-when-restoring-snapshot-in-5-x-with-base-path/102006/1 "2017-09-27T15:55:06Z")

</div>

I have a base path in Elasticsearch settings as follows "/es/sdb/" I understand that it is not supposed to have the leading "/" since it is deprecated, what about the trailing slash? Also with that setting I am getting an error saying no such key when trying to pull in a snapshot (from a 2.x cluster) ... using a different S3 repo without the base\_path works in the 5.x cluster. Any idea why?

EDIT: this is on Elastic cloud and trying to restore using Kopf that is installed there.

---

<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:** [October 25, 2017, 3:55pm UTC](https://discuss.elastic.co/t/s3-no-such-key-when-restoring-snapshot-in-5-x-with-base-path/102006/2 "2017-10-25T15:55:18Z")

</div>

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