# Configure an S3 compatible object storage provider for uploads

**URL:** <https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916>\
**Category:** Self-Hosting\
**Tags:** cdn, configuring, how-to, reference\
**Created:** [April 22, 2020, 10:37pm UTC](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916 "2020-04-22T22:37:37Z")\
**Posts on this page:** 1\
**Showing post:** 480

<div class="post-metadata">

**Author:** ![JamesNorth](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jamesnorth/32/283740_2.png) [@JamesNorth](https://meta.discourse.org/u/JamesNorth)\
**Post date:** [April 16, 2025, 1:45am UTC](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916/480 "2025-04-16T01:45:08Z")

</div>

> [@JamesNorth](#):
>
> iDrive Config

I just wanted to add to this post of mine with instructions on how to use iDrive’s E2.

There appears to be a thing that [iDrive has recently switched on](https://www.idrive.com/s3-storage-e2/rclone) that causes access keys that are assigned only to one bucket to fail unless a bucket auth check is bypassed.

You can bypass this when using `rclone` with `no_check_bucket = true` in the `rclone.conf` file, but I’m not sure such an ENV setting exists for Discourse building.

As a result, with iDrive E2, you currently _must_ use a key that has access to write to all your buckets, rather than just one.

---

_[View the full topic](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916)._