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

<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`

---

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