# 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:** 8
**Page:** 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).

---

<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: [August 17, 2024, 12:56pm UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/2 "2024-08-17T12:56:08Z")

</div>

It might be a better choice to declare those values in `app.yml` instead.

To answer your question, Yes, the settings for S3 are the same regardless of if you’re using amazon or any other S3 compatible service.

---

<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, 3:09pm UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/3 "2024-08-17T15:09:25Z")

</div>

> [@itsbhanusharma](#):
>
> It might be a better choice to declare those values in `app.yml` instead.

I thought it’d be better thru Admin settings, which we can change any time wo needing to rebuild our container. 😀 🙂

> [@itsbhanusharma](#):
>
> the settings for S3 are the same regardless of if you’re using amazon or any other S3 compatible service.

Great!!

---

<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 19, 2024, 8:00am UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/4 "2024-08-19T08:00:39Z")

</div>

> [@itsbhanusharma](#):
>
> Yes, the settings for S3 are the same regardless of if you’re using amazon or any other S3 compatible service

> [@Extend built-in backup remote destination options](https://meta.discourse.org/t/extend-built-in-backup-remote-destination-options/247769/4):
>
> IDrive actually supports the API of Amazon S3,

It seems it doesn’t.  
When I fill idrive’s S3 values in disco admin settings, it refuses to accept iDrive’s endpoint address:

 ![image](https://global.discourse-cdn.com/meta/original/4X/6/c/9/6c97c1255a6630051c6e122aeec7778471f27fa5.png)

Pls tell if I’m missing something here? I’ve filled iDrive’s Access Keys and Secret, but can’t test them till this is sorted out.  
Also there is no value supplied by iDrive to be filled in `S3 Cdn Url`

---

<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: [August 19, 2024, 9:00am UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/5 "2024-08-19T09:00:38Z")

</div>

> [@Bathinda](#):
>
> `S3 Cdn Url`

Only needed if idrive actually offers CDN for their storage. Alternatively you can use [bunny.net](http://bunny.net) for cdn if needed.

> [@Bathinda](#):
>
> it refuses to accept iDrive’s endpoint address

Did you try adding `https://`

---

<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 19, 2024, 9:02am UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/6 "2024-08-19T09:02:39Z")

</div>

> [@itsbhanusharma](#):
>
> Did you try adding `https://`

I tried now. But it still gives same ‘wrong format’ error.

---

<div class="post-metadata">

### Author: ![Alon1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alon1/32/197167_2.png) [@Alon1](https://meta.discourse.org/u/Alon1)
#### Post date: [September 3, 2024, 10:14pm UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/7 "2024-09-03T22:14:22Z")

</div>

I noticed that IDrive supports the S3 API according to IDrive documentation, but I haven’t tried using it IDrive as an S3 backup for Discourse.

---

<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: [September 7, 2024, 6:06am UTC](https://meta.discourse.org/t/adding-idrive-as-s3-service/322230/8 "2024-09-07T06:06:18Z")

</div>

I now noticed that although it accepted the endpoint value NOW with https, but the idrive bucket is still not reachable.
