# Path\_style\_acces option for V6.2

**URL:** <https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [July 26, 2021, 4:07am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586 "2021-07-26T04:07:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sonujatav35](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sonujatav35/32/90308_2.png) [@sonujatav35](https://discuss.elastic.co/u/sonujatav35)\
**Post date:** [July 26, 2021, 4:07am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586/1 "2021-07-26T04:07:06Z")

</div>

Hi,  
Any work around for Elasticsearch v6.2. My s3 compatible storage only accept path\_style\_access request and this option does not exist in ES v6. How can i make it work so s3 plugin can use path\_style\_access instead of using virtual style access in V6.2.

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:** [July 26, 2021, 4:52am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586/2 "2021-07-26T04:52:18Z")

</div>

If you upgrade to 7.13 (which you should do anyway), I think that this setting is available again: [Client Settings | Elasticsearch Plugins and Integrations [7.13] | Elastic](https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3-client.html)

---

<div class="post-metadata">

**Author:** ![sonujatav35](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sonujatav35/32/90308_2.png) [@sonujatav35](https://discuss.elastic.co/u/sonujatav35)\
**Post date:** [July 27, 2021, 4:25am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586/3 "2021-07-27T04:25:52Z")

</div>

Actually many elasticsearch services running with v5 and v6. To up-grade by v7 may takes some time.  
Is there any other solution for v6 apart from the up-gradation.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [July 27, 2021, 5:37am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586/4 "2021-07-27T05:37:55Z")

</div>

If your storage _requires_ path-style access then it's not really "S3-compatible" since S3 doesn't require path-style access, and indeed [path-style access is being entirely removed from S3](https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/). I suggest working with your storage supplier to address this.

6.2 is really old, long past [EOL](https://www.elastic.co/support/eol), you should also upgrade as a matter of urgency. One of the improvements in more recent versions is support for Minio which does still expect path-style access. I don't know of any other solution, but then the version you're using is so old that I don't have a working development environment for it any more so I can't even look at the code to check.

---

<div class="post-metadata">

**Author:** ![sonujatav35](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sonujatav35/32/90308_2.png) [@sonujatav35](https://discuss.elastic.co/u/sonujatav35)\
**Post date:** [July 28, 2021, 7:00am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586/5 "2021-07-28T07:00:13Z")

</div>

okay, got it.  
Thanks for the suggestion.

---

<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:** [August 25, 2021, 7:01am UTC](https://discuss.elastic.co/t/path-style-acces-option-for-v6-2/279586/6 "2021-08-25T07:01:04Z")

</div>

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