# S3 Snapshot issues

**URL:** <https://discuss.elastic.co/t/s3-snapshot-issues/232096>\
**Category:** Elasticsearch\
**Created:** [May 11, 2020, 6:40pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096 "2020-05-11T18:40:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Elk\_huh](https://avatars.discourse-cdn.com/v4/letter/e/d26b3c/32.png) [@Elk\_huh](https://discuss.elastic.co/u/Elk_huh)\
**Post date:** [May 11, 2020, 6:40pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/1 "2020-05-11T18:40:01Z")

</div>

I am trying to set up S3 snapshots and i keep getting this error, anyone has any ideas ?

```
  "error" : {
    "root_cause" : [
      {
        "type" : "repository_verification_exception",
        "reason" : "[s3] path is not accessible on master node"
      }
    ],
    "type" : "repository_verification_exception",
    "reason" : "[s3] path is not accessible on master node",
    "caused_by" : {
      "type" : "i_o_exception",
      "reason" : "Unable to upload object [tests-SZM1dzKDSgicfmnjCdwcfg/master.dat] using a single upload",
      "caused_by" : {
        "type" : "sdk_client_exception",
        "reason" : "Unable to execute HTTP request: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
        "caused_by" : {
          "type" : "s_s_l_handshake_exception",
          "reason" : "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
          "caused_by" : {
            "type" : "validator_exception",
            "reason" : "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
            "caused_by" : {
              "type" : "sun_cert_path_builder_exception",
              "reason" : "unable to find valid certification path to requested target"
            }
          }
        }
      }
    }
  },
  "status" : 500
}
```

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [May 11, 2020, 6:42pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/2 "2020-05-11T18:42:38Z")

</div>

@Elk_huh are you using actual AWS S3 or are you working with a third party implementation like Minio?

It looks like your nodes have trouble validating the SSL certificate used by the S3 endpoint. If this is not AWS S3 and you're using a third party S3 implementation, then you'll have to add its certificate to the secret store used by your ES nodes to fix this.

---

<div class="post-metadata">

**Author:** ![Elk\_huh](https://avatars.discourse-cdn.com/v4/letter/e/d26b3c/32.png) [@Elk\_huh](https://discuss.elastic.co/u/Elk_huh)\
**Post date:** [May 11, 2020, 6:53pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/3 "2020-05-11T18:53:33Z")

</div>

I am using repository-S3 for snapshots

---

<div class="post-metadata">

**Author:** ![Elk\_huh](https://avatars.discourse-cdn.com/v4/letter/e/d26b3c/32.png) [@Elk\_huh](https://discuss.elastic.co/u/Elk_huh)\
**Post date:** [May 11, 2020, 6:54pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/4 "2020-05-11T18:54:22Z")

</div>

> [@Armin\_Braun](#):
>
> you're using a third party S3 implementation, then you'll have to add its certificate

The problem is we have Zsacler in the middle doing SSl inspections , i have a slight suspicion that is part of the ossie

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [May 11, 2020, 7:30pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/5 "2020-05-11T19:30:00Z")

</div>

> [@Elk\_huh](#):
>
> I am using repository-S3 for snapshots

Sorry for being unclear here, my question was rather geared at whether or not you're setting a custom `endpoint` setting for your S3 repository and are using something like Minio/Ceph/etc. not at the plugin itself.

> [@Elk\_huh](#):
>
> The problem is we have Zsacler in the middle doing SSl inspections , i have a slight suspicion that is part of the ossie

Possibly, though I have to admit that I don't know anything about `Zsacler` so I couldn't say.

---

<div class="post-metadata">

**Author:** ![Elk\_huh](https://avatars.discourse-cdn.com/v4/letter/e/d26b3c/32.png) [@Elk\_huh](https://discuss.elastic.co/u/Elk_huh)\
**Post date:** [May 11, 2020, 7:31pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/6 "2020-05-11T19:31:26Z")

</div>

> [@Armin\_Braun](#):
>
> uestion was rather geared at whether or not you're setting a custom `endpoint` set

I am not doing anything custom. Just trying to add a access\_key / secret and trying to put into the bucekt

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [May 11, 2020, 7:34pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/7 "2020-05-11T19:34:06Z")

</div>

> [@Elk\_huh](#):
>
> I am not doing anything custom. Just trying to add a access\_key / secret and trying to put into the bucekt

In that case `Zsacler` is the most likely culprit here I think (from what I could gather through a little Google you probably have to do some config work there to get the certificate used by S3 working).

---

<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:** [June 8, 2020, 7:34pm UTC](https://discuss.elastic.co/t/s3-snapshot-issues/232096/8 "2020-06-08T19:34:15Z")

</div>

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