# Is repository-s3 plugin fixed in 6.3?

**URL:** <https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997>\
**Category:** Elasticsearch\
**Created:** [June 14, 2018, 7:41pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997 "2018-06-14T19:41:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![windowsrefund\_refund](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/windowsrefund_refund/32/72734_2.png) [@windowsrefund\_refund](https://discuss.elastic.co/u/windowsrefund_refund)\
**Post date:** [June 14, 2018, 7:41pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997/1 "2018-06-14T19:41:51Z")

</div>

Running 6.2.4 here and repository-s3 plugin is not allowing me to create a repository despite the fact I have used the new elasticsearch-keystore binary to create both s3.client.default.access\_key and s3.client.default.secret\_key

`{"error":{"root_cause":[{"type":"repository_exception","reason":"[my_s3_repository1] failed to create repository"}],"type":"repository_exception","reason":"[my_s3_repository1] failed to create repository","caused_by":{"type":"sdk_client_exception","reason":"Unable to load credentials from service endpoint","caused_by":{"type":"socket_timeout_exception","reason":"connect timed out"}}},"status":500}[root@cb5e3dd9d478`

After hunting around, I'm thinking this might be fixed in the 6.3 release...

> <https://github.com/elastic/elasticsearch/pull/30652>

Can anyone confirm I'm reading this right?

---

<div class="post-metadata">

**Author:** ![Albert\_Zaharovits](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/albert_zaharovits/32/24390_2.png) [@Albert\_Zaharovits](https://discuss.elastic.co/u/Albert_Zaharovits)\
**Post date:** [June 22, 2018, 4:28pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997/2 "2018-06-22T16:28:40Z")

</div>

Hello @windowsrefund_refund

I could not reproduce the problem you are describing. In general, it is advisable to paste the stack trace of the exception on the elasticsearch side to get a more accurate diagnosis.  
However, I think I know what the problem is:  
The keystore needs to be populated with

```auto
  bin/elasticsearch-keystore add s3.client.default.secret_key
  bin/elasticsearch-keystore add s3.client.default.access_key

```

**before** you start elasticsearch `./bin/elasticsearch`.  
If you have added the entries to the keystore after elasticsearch was started, you need to restart it.  
Then, registering the repository should be a breeze:

```auto
curl -X PUT "localhost:9200/_snapshot/my_s3_repository" -H 'Content-Type: application/json' -d'
{
  "type": "s3",
  "settings": {
    "bucket": "elasticsearch.test.bucket"
  }
}
'

```

NB: The GH issue you have pasted is not related to the matter at hand.

---

<div class="post-metadata">

**Author:** ![windowsrefund\_refund](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/windowsrefund_refund/32/72734_2.png) [@windowsrefund\_refund](https://discuss.elastic.co/u/windowsrefund_refund)\
**Post date:** [June 25, 2018, 3:46pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997/3 "2018-06-25T15:46:59Z")

</div>

Hello and thanks for the response. I've set both s3.client.default.access\_key and s3.client.default.secret\_key using the elasticsearch-keystore binary on 1 of my nodes. This has been verified by running elasticsearch-keystore with the list option. However, upon restarting the elasticsearch service, I see this error in the log

> at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_111]  
> Caused by: java.lang.IllegalArgumentException: Setting [access\_key] is insecure, but property [allow\_insecure\_settings] is not set

Is this allow\_insecure\_setting config needed? Docs certainly say nothing about it. Also, do I need to do this work on every node in the cluster or only 1? Docs say nothing about that as well.

---

<div class="post-metadata">

**Author:** ![windowsrefund\_refund](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/windowsrefund_refund/32/72734_2.png) [@windowsrefund\_refund](https://discuss.elastic.co/u/windowsrefund_refund)\
**Post date:** [June 25, 2018, 6:46pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997/4 "2018-06-25T18:46:37Z")

</div>

OK so it turns out elasticsearch-keystore needs to be set on every node in the cluster. Why on earth this simple sentence is not present in the existing documentation is beyond me.

---

<div class="post-metadata">

**Author:** ![Albert\_Zaharovits](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/albert_zaharovits/32/24390_2.png) [@Albert\_Zaharovits](https://discuss.elastic.co/u/Albert_Zaharovits)\
**Post date:** [June 27, 2018, 6:19pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997/5 "2018-06-27T18:19:48Z")

</div>

@windowsrefund_refund I am sorry for the frustration, I have opened [https://github.com/elastic/elasticsearch/pull/31621](https://github.com/elastic/elasticsearch/pull/31621)

---

<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:** [July 25, 2018, 6:19pm UTC](https://discuss.elastic.co/t/is-repository-s3-plugin-fixed-in-6-3/135997/6 "2018-07-25T18:19:49Z")

</div>

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