# ES 6.4.0 repository S3 issue

**URL:** <https://discuss.elastic.co/t/es-6-4-0-repository-s3-issue/284238>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [September 15, 2021, 2:43am UTC](https://discuss.elastic.co/t/es-6-4-0-repository-s3-issue/284238 "2021-09-15T02:43:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![theMike](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/themike/32/94568_2.png) [@theMike](https://discuss.elastic.co/u/theMike)\
**Post date:** [September 15, 2021, 2:43am UTC](https://discuss.elastic.co/t/es-6-4-0-repository-s3-issue/284238/1 "2021-09-15T02:43:44Z")

</div>

Hi,  
I'm trying to use repository-s3 to snapshot a single node ELK instance to our StorageGrid via S3 api.

```auto
{
 "type": "s3",
 "settings": {
   "endpoint": "objectstore.xxxx.xxx:xxxx",
   "bucket": "our-elk-backup"
 }
}

```

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

```

All user groups have full access permissions

```auto
{
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": "urn:sgws:s3:::*"
        }
    ]
}

```

Using the latest aws-cli from the ELK server I'm able to read and write to all buckets however when trying to register a snapshot the following error is returned:

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "repository_verification_exception",
        "reason" : "[elk-backup] path is not accessible on master node"
      }
    ],
    "type" : "repository_verification_exception",
    "reason" : "[elk-backup] path is not accessible on master node",
    "caused_by" : {
      "type" : "i_o_exception",
      "reason" : "Unable to upload object [tests-NXVHCLNAQx-BL554v1CyUA/master.dat] using a single upload",
      "caused_by" : {
        "type" : "amazon_s3_exception",
        "reason" : "Method Not Allowed (Service: Amazon S3; Status Code: 405; Error Code: 405 Method Not Allowed; Request ID: null; S3 Extended Request ID: null)"
      }
    }
  },
  "status" : 500
}

```

From similar threads, there is the suggestion that this may be an API compatibility issue however how does that explain why the latest aws-cli works?

If all else fails, would using S3FS be an alternative here?

Thanks.

---

<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:** [September 15, 2021, 5:20am UTC](https://discuss.elastic.co/t/es-6-4-0-repository-s3-issue/284238/2 "2021-09-15T05:20:22Z")

</div>

I'd start a 7.14.1 cluster and try to register the repository on that test cluster.

You can also try with 6.8.x.

Then I'd recommend to at least upgrade to 6.8 but better to 7.14.

---

<div class="post-metadata">

**Author:** ![theMike](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/themike/32/94568_2.png) [@theMike](https://discuss.elastic.co/u/theMike)\
**Post date:** [September 21, 2021, 6:32pm UTC](https://discuss.elastic.co/t/es-6-4-0-repository-s3-issue/284238/3 "2021-09-21T18:32:55Z")

</div>

Thanks, tried it with 7.9.1 and it worked.

---

<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 19, 2021, 6:33pm UTC](https://discuss.elastic.co/t/es-6-4-0-repository-s3-issue/284238/4 "2021-10-19T18:33:52Z")

</div>

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