# Extend S3 configuration for other S3 API compatible services

**URL:** <https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371>\
**Category:** Feature\
**Created:** [21.Июнь.2018 07:10:42 UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371 "2018-06-21T07:10:42Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![rishabh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rishabh/32/179446_2.png) [@rishabh](https://meta.discourse.org/u/rishabh)\
**Post date:** [28.Июнь.2018 15:46:48 UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371/17 "2018-06-28T15:46:48Z")

</div>

> [@Falco](#):
>
> If both Google and Minio work without the region then let’s ship it.

All 3 platforms will not require an additional `region` field and the current PR will add support for DigitalOcean Spaces and Minio.

1. **Minio** : _endpoint format: server\_ip:9000 or user domain_  
Requires `region` but it works perfectly with the pre-existing `s3_region` options (drop-down menu) in site settings so it does not need an extra `region` field.

2. **Google Cloud Platform** : _endpoint format: [https://storage.googleapis.com](https://storage.googleapis.com)_  
Does not require a `region` parameter but I haven’t got it to work yet because of an incorrect header issue that I’m investigating but it will work without an extra `region` field once I debug the issue.

3. **DigitalOcean Spaces** : _endpoint format: [https://nyc3.digitaloceanspaces.com](https://nyc3.digitaloceanspaces.com)_  
Works perfectly without an extra `region` field.

* * *

@Falco Before we ship it, the last problem is that Minio requires `{ force_path_style: true }` in s3\_options and AWS requires the setting to be `false.` This is because AWS and Minio use different addressing styles so if we force one, it breaks the other.  
I know we wanted to avoid this but I don’t see how we can make both work without adding something specific like this:

```plaintext
if opts[:endpoint].includes? "minio"
  opts[:force_path_style] = true 

```

But even this won’t work because a lot of Minio users might use IP addresses to their servers instead of having “minio” in their endpoint. We have to think of a way to detect a Minio endpoint and we might need Minio specific code in Discourse if we want to support it.

We could support a lot of cloud options easily if we could have a free-text field for entering key:pair options for greater flexibility and avoiding issues like this. The `region` and `force_path_style` issues would be solved. @riking What do you feel about a field like this?

---

_[View the full topic](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371)._
