Other S3
Any service with an S3-compatible API works with Guyun — your provider supplies the endpoint and the key, and only the details differ.
Have three things ready: endpoint / bucket name / key (the region is handled by the app). The endpoint cannot be derived, so copy it from your provider's docs.
Step by step
-
Step 1
Check that it really is S3-compatible
- Your provider's docs should mention S3-compatible, S3 API or similar and give an S3 endpoint: either
https://s3.<region>.<provider-domain>or an account-specific one such ashttps://<account>.r2.cloudflarestorage.com. - A service with only a web upload page and no S3 endpoint cannot be connected. Cloudflare R2, Backblaze B2, MinIO, Upyun, Qiniu, and the S3-compatible interfaces of Alibaba Cloud OSS and Tencent Cloud COS all belong to the first group.
- Your provider's docs should mention S3-compatible, S3 API or similar and give an S3 endpoint: either
-
Step 2
Create a private bucket and a key limited to it
- Create a private bucket with your own provider (do not turn on public read or write).
- Then create an access key pair that is limited to that bucket — use a sub-account or an API token rather than the main account's key.
-
Step 3
Find the three values in your provider's docs
- Find these three values: endpoint, bucket name, and access key ID and secret.
- Providers name them differently (Key ID, Application Key, API token, SecretId …) — use the table below to match them up.
-
Step 4
Fill them in and test
- In Guyun open Add storage, choose Other S3 and enter the three values.
- Then choose Test connection & save.
The names providers commonly use
What the three values are called elsewhere, and where to find them:
| Name in Guyun | Common names | Where to find it |
|---|---|---|
| Endpoint | S3 Endpoint / API Endpoint / service URL | The “S3 API” section of your provider's docs |
| Bucket name | Bucket / container | The bucket list in your provider's console |
| Key | Access Key ID + Secret / Key ID + Application Key / API token | Your provider's “API keys” or “access keys” page |
Other cases (skip if not needed)
The three most common traps, and what “S3-compatible” does not promise.
The three most common traps
- The endpoint is the console address. Guyun needs the S3 API endpoint, not the web address you open the provider's console at in a browser.
- The endpoint contains a bucket name or path. Guyun wants the host name only; the bucket name and the path have their own fields.
- The bucket name is abbreviated. Some providers want the account ID or APPID suffix attached (as in
your-bucket-name-1234567890) — use the full name shown in the provider's bucket list.
Feature differences
- S3-compatible does not mean feature-complete: some providers have no server-side image processing, or lack thumbnails and some multipart upload parameters.
- Browsing and transfers in Guyun are unaffected; only thumbnails may not show for such buckets, so download the file to see it.
Authoritative references
- Amazon S3 API Reference (the API that “compatible” means) (opens in a new tab)
- (External reference) Virtual-hosted and path-style addressing (AWS docs) (opens in a new tab)
Copy these three values
They go into the matching fields on Guyun's "Add storage" screen: Endpoint: Other S3 has no preset place — type the S3 endpoint from your provider's docs into the app's HTTPS endpoint field (e.g. https://s3.<region>.<provider domain>); the bucket name and key go in as the table above says.
| This value | Where it goes in Guyun |
|---|---|
| Bucket name The full bucket name shown in your provider's console; some providers want the account ID or APPID suffix attached, e.g. your-bucket-name-1234567890. | Bucket name |
| Endpoint The S3 endpoint from your provider's docs: host name only, e.g. https://s3.<region>.<provider-domain>, with no bucket name and no path. | Endpoint |
| Key The key pair limited to that bucket: access key ID and secret (sometimes Key ID and Application Key). | Access key ID and secret |
How to tell it worked
- The connection test passes, which means this key can read this bucket; Guyun only lists the root directory and changes nothing.
- If it fails, check the endpoint, bucket name and key first, then the place; otherwise see common errors.
Go back to Guyun and choose Test connection & save.