# Setup snapshot for s3 plugin

**URL:** <https://discuss.elastic.co/t/setup-snapshot-for-s3-plugin/211661>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [December 12, 2019, 2:12pm UTC](https://discuss.elastic.co/t/setup-snapshot-for-s3-plugin/211661 "2019-12-12T14:12:54Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [December 20, 2019, 10:53am UTC](https://discuss.elastic.co/t/setup-snapshot-for-s3-plugin/211661/12 "2019-12-20T10:53:44Z")

</div>

I'm not very familiar with the s3 repository, but by looking around I guess:

- either there is a problem with secure settings themselves (wrong value or not set correctly), see [Error while creating snapshot to s3 repository](https://discuss.elastic.co/t/error-while-creating-snapshot-to-s3-repository/176731)  
Can you double-check your `s3.client.default.access_key` and `s3.client.default.secret_key` are correct? Note their value should be base64-encoded in the Kubernetes secret.

- either the host on which Elasticsearch is running cannot reach aws metadata server, see [https://stackoverflow.com/questions/58378329/aws-instance-metadata-for-iam-is-not-found](https://stackoverflow.com/questions/58378329/aws-instance-metadata-for-iam-is-not-found)

---

_[View the full topic](https://discuss.elastic.co/t/setup-snapshot-for-s3-plugin/211661)._