# 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:** 6

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [27.Июнь.2018 06:39:39 UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371/6 "2018-06-27T06:39:39Z")

</div>

Can you put your code changes up as a PR on Github?

Also, that setting is being inserted as `Aws::S3::Resource.new(... endpoint ...)`, right?  
The setting should be named `s3_endpoint`, default of `https://s3.amazonaws.com` – as it’s not specific to DO Spaces.

---

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