# 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:** [June 21, 2018, 7:10am 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:** 5

<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: [June 27, 2018, 6:06am UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371/5 "2018-06-27T06:06:33Z")

</div>

> [@Extend S3 configuration for other s3 API compatible cloud storage solutions](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-cloud-storage-solutions/20593/20):
>
> #pr-welcome for this but I do want full details about the site setting changes to be made prior to implementing anything.

@sam I’ve made this work by adding one optional field named _spaces\_endpoint_ to site settings.  
This enables Spaces support for all existing S3 features like upload, delete etc.  
Does this look fine to you?

```plaintext
spaces_endpoint:
    default: ''

```

* * *

Here’s an image of the new Settings/Files page:

 ![Screenshot%20from%202018-06-27%2010-28-35](https://global.discourse-cdn.com/meta/original/3X/b/b/bb74055e29d4cb7d4365a6b5097570e2378abc75.png)

---

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