# Adding idrive as S3 service

**URL:** <https://meta.discourse.org/t/adding-idrive-as-s3-service/322230>\
**Category:** Self-hosting\
**Tags:** s3\
**Created:** [August 17, 2024, 12:33pm UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230 "2024-08-17T12:33:39Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Bathinda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bathinda/32/135888_2.png) [@Bathinda](https://meta.discourse.org/u/Bathinda)\
**Post date:** [August 17, 2024, 12:33pm UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/1 "2024-08-17T12:33:39Z")

</div>

> [@Extend built-in backup remote destination options](https://meta.discourse.org/t/extend-built-in-backup-remote-destination-options/247769/4):
>
> I just stumbled on it today but IDrive actually supports the API of Amazon S3, it means you theoretically can use Discourse backup to S3, just with a very cheap “e2” and your Discourse won’t know the difference.  
> see `https://www.idrive.com/e2/`

Do you mean I just need to fill the values demanded by Aws\_S3 fields in Disco Admin Settings with the values provided by iDrive S3? (because there are no other fields in the disco admin settings for any other S3 service).

---

_[View the full topic](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230)._