# The issue with Elasticsearch 6.8 & repository-s3

**URL:** <https://discuss.elastic.co/t/the-issue-with-elasticsearch-6-8-repository-s3/299984>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [March 17, 2022, 7:05pm UTC](https://discuss.elastic.co/t/the-issue-with-elasticsearch-6-8-repository-s3/299984 "2022-03-17T19:05:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtsunne](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jtsunne/32/103185_2.png) [@jtsunne](https://discuss.elastic.co/u/jtsunne)\
**Post date:** [March 17, 2022, 7:05pm UTC](https://discuss.elastic.co/t/the-issue-with-elasticsearch-6-8-repository-s3/299984/1 "2022-03-17T19:05:02Z")

</div>

I'm facing a strange issue.

It was working 6 months ago.

Elasticsearch version 6.8.12 was created based on the CentOS Linux release 7.9.2009 (Core) from RPM (we are using Puppet)

```auto
{
"name": "az-es68-master-1",
"cluster_name": "az-XXXXXX-v68",
"cluster_uuid": "1suO-i2ESGGT5iSmAbaYVQ",
"version": {
"number": "6.8.12",
"build_flavor": "default",
"build_type": "rpm",
"build_hash": "7a15d2a",
"build_date": "2020-08-12T07:27:20.804867Z",
"build_snapshot": false,
"lucene_version": "7.7.3",
"minimum_wire_compatibility_version": "5.6.0",
"minimum_index_compatibility_version": "5.0.0"
},
"tagline": "You Know, for Search"
}

```

Installed 3 plugins

```auto
/usr/share/elasticsearch/bin/elasticsearch-plugin list
mapper-size
repository-azure
repository-s3

```

Credentials stored in keystore

```auto
/usr/share/elasticsearch/bin/elasticsearch-keystore list
azure.client.default.account
azure.client.default.key
keystore.seed
s3.client.default.access_key
s3.client.default.secret_key

```

When I try to create a repository I see:

```auto
curl -XPUT -H 'Content-Type: application/json' 'http://localhost:9200/_snapshot/es68-prod' -d '{"type": "s3","settings": {"bucket": "XXXXX-es68","region": "us-east-2", "readonly": true}}'

{"error":{"root_cause":[{"type":"repository_verification_exception","reason":"[es68-prod] path is not accessible on master node"}],"type":"repository_verification_exception","reason":"[es68-prod] path is not accessible on master node","caused_by":{"type":"i_o_exception","reason":"Exception when listing blobs by prefix [index-]","caused_by":{"type":"amazon_s3_exception","reason":"The request signature we calculated does not match the signature you provided. Check your key and signing method. (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: DYSV72X98F8PWXG5; S3 Extended Request ID: Ywu948NpnnHtYgytOn1zswxyVXhzF+FP07DOnqbnnUOLqKVDLyvcjxR0nq5g2HMnZLso+R+1YqA=)"}}},"status":500}

```

What it can be?

Elasticsearch.yml is

```auto
### DO NOT MODIFY THIS FILE...
### It is managed by puppet...

# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# --------------------------------- Variable ----------------------------------
cluster.name: az-XXXXXX-v68
node.name: az-es68-master-1
node.data: false
node.master: true
node.attr.tag: aws
node.attr.search: no
node.attr.indexing: no

network.host: [10.10.2.12, localhost]
path.data: /var/lib/elasticsearch/data/
path.logs: /var/lib/elasticsearch/logs/
path.repo: ["/var/backup/elasticsearch"]

http.compression: true

# --------------------------------- Discovery ---------------------------------
discovery.zen.ping.unicast.hosts:
    - az-es68-master-1
    - az-es68-master-2
    - az-es68-master-3
discovery.zen.minimum_master_nodes: 2

# --------------------------------- X-Pack ---------------------------------
xpack.security.enabled: false
xpack.ml.enabled: false
xpack.monitoring.enabled: false
xpack.watcher.enabled: false
reindex.remote.whitelist: "*.*"

```

AWS credentials are working (double-checked and verified).

What I tried (but not helped):

- Use latest JDK (java-1.8.0-openjdk-1.8.0.322.b06-1.el7\_9.x86\_64)
- Use downgraded JDK (java-1.8.0-openjdk-headless-1.8.0.262.b10-0.el7\_8.x86\_64)
- Use the latest Elasticsearch (v.6.8.23)
- Use the latest Elasticsearch (v.7.17.1)

It was worked one year ago, and it was worked six months ago.  
What are the settings I lost?

Thanks for any ideas

---

<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:** [March 17, 2022, 7:05pm UTC](https://discuss.elastic.co/t/the-issue-with-elasticsearch-6-8-repository-s3/299984/2 "2022-03-17T19:05:03Z")

</div>

Elasticsearch 6.8 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<div class="post-metadata">

**Author:** ![jtsunne](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jtsunne/32/103185_2.png) [@jtsunne](https://discuss.elastic.co/u/jtsunne)\
**Post date:** [March 18, 2022, 11:24pm UTC](https://discuss.elastic.co/t/the-issue-with-elasticsearch-6-8-repository-s3/299984/3 "2022-03-18T23:24:05Z")

</div>

Solved.

Found the issue in escaping credentials.

---

<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 15, 2022, 11:24pm UTC](https://discuss.elastic.co/t/the-issue-with-elasticsearch-6-8-repository-s3/299984/4 "2022-04-15T23:24:07Z")

</div>

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