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

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [June 21, 2018, 7:14am UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371/2 "2018-06-21T07:14:08Z")

</div>

Some insight here:

> [@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/24):
>
> Step 1: Demonstrating in code how you would get aws-s3 gem to talk to a different provider. I have not researched that yet but that is the first blocker here. This may not be trivial considering amazon are the ones maintaining that gem.

For development, start with a local development sandbox.

Discourse can be a good starting point as your first ruby app as well.

---

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