# S3 Path Style Access

**URL:** https://meta.discourse.org/t/s3-path-style-access/131890
**Category:** Support
**Created:** [October 25, 2019, 5:13pm UTC](https://meta.discourse.org/t/s3-path-style-access/131890 "2019-10-25T17:13:44Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![recursivecodes](https://avatars.discourse-cdn.com/v4/letter/r/6de8d8/32.png) [@recursivecodes](https://meta.discourse.org/u/recursivecodes)
#### Post date: [October 25, 2019, 5:13pm UTC](https://meta.discourse.org/t/s3-path-style-access/131890/1 "2019-10-25T17:13:44Z")

</div>

I see that there was support for using “path style” access for S3 at one point, but it was removed. Can we figure out a compromise to get this added back in as well as support for chunked encoding? Some cloud providers S3 compatible endpoints require just a tiny bit more configuration and these two settings in particular are required to use Oracle Cloud Object Storage:

Removed in this commit:

[https://github.com/discourse/discourse/commit/ad6ad3f67972e74495cb424b95577e497c811b42](https://github.com/discourse/discourse/commit/ad6ad3f67972e74495cb424b95577e497c811b42)

Oracle Cloud Docs:

> **[Object Storage Amazon S3 Compatibility API](https://docs.oracle.com/en-us/iaas/Content/Object/Tasks/s3compatibleapi.htm)**
>
> Learn how to use Oracle Cloud Infrastructure's Amazon S3 Compatibility API, where you can use existing Amazon S3 tools to work with Object Storage.

Thanks!

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [October 25, 2019, 6:05pm UTC](https://meta.discourse.org/t/s3-path-style-access/131890/2 "2019-10-25T18:05:54Z")

</div>

Reasoning for the change is here:

> [@Minio not supported in the newest version?](https://meta.discourse.org/t/minio-not-supported-in-the-newest-version/119610/2):
>
> Mínio supports “DNS style” buckets for over a year, and Amazon S3 is deprecating “path style” so there is no reason to keep that old setting and all the complexity it had.

So we have compatibility with AWS S3, Google Cloud Storage, Digital Ocean Spaces. I’m afraid compatibility with Oracle Cloud won’t be enough to justify the added complexity in core.

Doesn’t Oracle plans on fixing this in their roadmap? If not, the only road would be adding the path style support in a custom plugin.

---

<div class="post-metadata">

### Author: ![recursivecodes](https://avatars.discourse-cdn.com/v4/letter/r/6de8d8/32.png) [@recursivecodes](https://meta.discourse.org/u/recursivecodes)
#### Post date: [October 25, 2019, 8:04pm UTC](https://meta.discourse.org/t/s3-path-style-access/131890/3 "2019-10-25T20:04:11Z")

</div>

> [@Falco](#):
>
> Doesn’t Oracle plans on fixing this in their roadmap?

I’ll work on this. Thanks for the quick reply.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [November 24, 2019, 8:06pm UTC](https://meta.discourse.org/t/s3-path-style-access/131890/4 "2019-11-24T20:06:52Z")

</div>

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