Connect Opndrive to any S3-compatible storage

If a service speaks the S3 API, this is the way in. You supply the endpoint URL and the region string that service documents, and from there Opndrive treats it exactly as it treats Amazon S3.

Provider

Selected

Custom endpointAny other S3-compatible serviceChange

Add credentials

Open your drive

Setting up Custom endpointOptional

1. Allow this site in CORS

Look for CORS, cross-origin or allowed origins in the bucket settings on your provider. Most accept the same JSON policy S3 does; some expose it only through their CLI or API, and a few need a support request.

2. Paste this policy

{
    "AllowedMethods": [
        "GET",
        "PUT",
        "POST",
        "DELETE",
        "HEAD"
    ],
    "AllowedOrigins": [
        "https://your-domain.com"
    ],
    "AllowedHeaders": [
        "*"
    ],
    "ExposeHeaders": [
        "ETag"
    ],
    "MaxAgeSeconds": 3000
}

Replace https://your-domain.com with the address you use Opndrive from.

3. Permissions the key needs

s3:GetObject
s3:PutObject
s3:DeleteObject
s3:ListBucket

Worth knowing

Use the S3 API endpoint, not the web console address or the public link to a file. A provider often serves all three from similar-looking domains and only one of them speaks S3. If the bucket lists but files will not open, that is CORS rather than the endpoint.

The S3 CORS API that compatible services implement