Theme
Other S3 compatible providers
Every S3 compatible store connects the same way: a VFS of type S3, the provider's endpoint, its region, an access key with its secret, and the right Use path style addressing setting. The other articles in this section cover the stores we see most often; this page gathers the settings for several more.
| Provider | Region | Endpoint | Path style |
|---|---|---|---|
| DigitalOcean Spaces | the Space's region, for example nyc3 | https://<region>.digitaloceanspaces.com | off |
| Hetzner Object Storage | the location, for example fsn1 | https://<location>.your-objectstorage.com | off |
| Scaleway Object Storage | for example fr-par | https://s3.<region>.scw.cloud | off |
| OVHcloud Object Storage | for example gra | https://s3.<region>.io.cloud.ovh.net | on |
| Storj | leave empty | https://gateway.storjshare.io | off |
| Oracle Cloud Infrastructure | the region, for example eu-frankfurt-1 | https://<namespace>.compat.objectstorage.<region>.oraclecloud.com | on |
| IDrive e2 | leave empty | the endpoint shown in the e2 console for your bucket | on |
In every case:
- The endpoint is the service URL, never the bucket URL: no bucket name in it.
- Create a dedicated access key limited to the bucket, never the account's root keys.
- Path style addressing works against every S3 compatible store; off is listed only where the provider documents a host name per bucket. If the connection test says a host such as
mybucket.<endpoint host>could not be resolved, turn the toggle on. - S3 compatible stores differ from each other in real ways, not just in the endpoint. Test a listing, an upload, a download and a delete before you hand the storage to users.
When you save, the Connector tests the storage right away. If it cannot reach it, the form stays open and says why.
In the manual