# Snapshot to S3 compatible storage issue **URL:** \ **Category:** Elasticsearch\ **Created:** [April 4, 2020, 11:50am UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510 "2020-04-04T11:50:00Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Sergey\_Mucha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sergey_mucha/32/61010_2.png) [@Sergey\_Mucha](https://discuss.elastic.co/u/Sergey_Mucha)\ **Post date:** [April 4, 2020, 11:50am UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510/1 "2020-04-04T11:50:00Z")
Stack ES 6.8.2 Minio S3 VERSION: 2019-10-12T01:39:57Z I have es cluster running. When I try to create repo for s3 on minio with { "type": "s3", "settings": { "bucket": "elasticsearch-backups", "endpoint": "dns-name" } } I get "error" : { "root\_cause" : [ { "type" : "repository\_verification\_exception", "reason" : "[es\_snapshot\_s3] path is not accessible on master node" } ], "type" : "repository\_verification\_exception", "reason" : "[es\_snapshot\_s3] path is not accessible on master node", "caused\_by" : { "type" : "i\_o\_exception", "reason" : "Unable to upload object [tests-KnN5zU85RRmeOSfqPWX1Pg/master.dat] using a single upload", "caused\_by" : { "type" : "sdk\_client\_exception", "reason" : "Unable to execute HTTP request: elasticsearch-backups.dns-name", "caused\_by" : { "type" : "unknown\_host\_exception", "reason" : "elasticsearch-backups.dns-name" } } } }, "status" : 500 } because there is no elasticsearch-backups.dns-name dns A record ``` at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91] ``` Caused by: java.net.UnknownHostException: elasticsearch-backups.dns-name at java.net.InetAddress.getAllByName0(InetAddress.java:1280) ~[?:1.8.0\_91] at java.net.InetAddress.getAllByName(InetAddress.java:1192) ~[?:1.8.0\_91] at java.net.InetAddress.getAllByName(InetAddress.java:1126) ~[?:1.8.0\_91] These is path\_style\_access option but I am not sure that it is available in 6.8.2 version ES. Can someone clarify? ---
**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:** [April 7, 2020, 8:08pm UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510/2 "2020-04-07T20:08:20Z")
Hi @Sergey_Mucha > [@Sergey\_Mucha](#): > > These is path\_style\_access option but I am not sure that it is available in 6.8.2 version ES. I'm afraid forcing path style access was only introduced in v7, see relevant PR here: > > > \* Add setting for forcing path style access to S3 client > \* Make tests use \`loca…lhost\` which without the setting leads to the S3 client going for DNS type access > \* Add setting with value \`true\` in ITs to force path style access again =\> Same functionality gets tested along with the setting taking effect > \* closes #31608 Could you maybe set an IP for the endpoint? That would be a workaround that would force the SDK to use path style access. ---
**Author:** ![Sergey\_Mucha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sergey_mucha/32/61010_2.png) [@Sergey\_Mucha](https://discuss.elastic.co/u/Sergey_Mucha)\ **Post date:** [April 8, 2020, 12:19pm UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510/3 "2020-04-08T12:19:08Z")
> [@Armin\_Braun](#): > > Could you maybe set an IP or the endpoint? I set endpoint, not sure that I get what you mean for endpoint. ---
**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:** [April 8, 2020, 12:32pm UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510/4 "2020-04-08T12:32:21Z")
> [@Sergey\_Mucha](#): > > I set endpoint, not sure that I get what you mean for endpoint. Sorry that was the worst possible typo 🙂 What I meant to write was that you should set an actual IP address for the endpoint, not a DNS name if that is possible. ---
**Author:** ![Sergey\_Mucha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sergey_mucha/32/61010_2.png) [@Sergey\_Mucha](https://discuss.elastic.co/u/Sergey_Mucha)\ **Post date:** [April 8, 2020, 12:37pm UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510/5 "2020-04-08T12:37:44Z")
> [@Armin\_Braun](#): > > Sorry that was the worst possible typo 🙂 What I meant to write was that you should set an actual IP address for the endpoint, not a DNS name if that is possible. 🙂 Ok. Now I get. hahaha. I used ip, but sometimes s3 will be with dnsname - it will require updates for s3 in case it use ssl(include ip address to alternative name). Anyway thanks for clarification. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 6, 2020, 12:37pm UTC](https://discuss.elastic.co/t/snapshot-to-s3-compatible-storage-issue/226510/6 "2020-05-06T12:37:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.