Provider connection guides
What to put in each field of the connection form, where the values come from, and the mistakes that cost an afternoon — one page per provider.
Connect S3 Explorer to Amazon S3: no endpoint to fill in, region-based routing, virtual-hosted addressing and temporary STS credentials.
Connect S3 Explorer to Google Cloud Storage through the interoperability API: fixed endpoint, HMAC keys, and why service account keys will not work.
Connect S3 Explorer to Cloudflare R2: account-scoped endpoint, mandatory path-style addressing, no regions and no egress fees.
Connect S3 Explorer to Backblaze B2 over the S3-compatible API: cluster-specific endpoints, keyID as access key, and both addressing styles supported.
Connect S3 Explorer to Wasabi hot cloud storage: AWS-shaped regions and credentials, region-specific endpoints, no per-request fees.
Connect S3 Explorer to DigitalOcean Spaces: region-based endpoints, virtual-hosted addressing only, and Spaces keys separate from the API token.
Connect S3 Explorer to OVHcloud Object Storage: datacenter-coded regions, S3 users created under Public Cloud, and the high-performance S3 endpoint.
Connect S3 Explorer to a MinIO server: full URL with port, mandatory path-style addressing, ignored regions, and the single-drive listing trap.
Connect S3 Explorer to Ceph RADOS Gateway: default port 7480, credentials from radosgw-admin, SigV2 and SigV4 both supported.
Connect S3 Explorer to Dell EMC ECS: namespace-scoped object users, the 9020/9021 port pair, and the Content-MD5 requirement on batch deletes.
Also supported
S3 Explorer ships a ready-made connection preset for each of these too — endpoint format, region list and addressing mode are filled in for you. They just do not have a detailed guide yet.
… and any other S3-compatible service through a custom endpoint.