# Using Scaleway s3-compatible object storage

**URL:** <https://meta.discourse.org/t/using-scaleway-s3-compatible-object-storage/140603>\
**Category:** Product Support\
**Created:** [4 בפברואר,‏ 2020,‏ 3:54pm UTC](https://meta.discourse.org/t/using-scaleway-s3-compatible-object-storage/140603 "2020-02-04T15:54:52Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![elle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elle/32/119940_2.png) [@elle](https://meta.discourse.org/u/elle)\
**Post date:** [10 באפריל,‏ 2020,‏ 10:21am UTC](https://meta.discourse.org/t/using-scaleway-s3-compatible-object-storage/140603/17 "2020-04-10T10:21:26Z")

</div>

the reason the s3 upload/backup does not work is the region that needs to be set to `fr-par` (or `nl-ams`) which can only be set by circumventing discourse’s SiteSetting validation:

(via `./launcher enter app` then `rails c`)

```plaintext
SiteSetting.find_by(name: 's3_region').update_attribute(:value, 'fr-par')

```

after this change uploads and backups work to scaleway object storage.

[Scaleway documentation on Object Storage](https://www.scaleway.com/en/docs/object-storage-feature/#-Core-Concepts)

of course, this is a workaround and once you reset or change this site setting via Web Admin you cannot set it back to a working state (unless using rails console again)

I guess the aws/s3 Client all allow explicitly setting a region string (as opposed to the current state of the webadmin)

It is also kind of misleading in case of the “EU (Paris)” dropdown value in discourse, since this refers to the aws naming scheme `eu-west-3` (or sth. like that) and not the expected value for scaleway.

---

_[View the full topic](https://meta.discourse.org/t/using-scaleway-s3-compatible-object-storage/140603)._