Client gotchas

AWS CLI ignores my endpoint

You must pass --endpoint-url "https://YOUR-ENDPOINT/" on each command (or script it via a wrapper). Without it, the CLI talks to AWS, not your node. See client examples.

rclone can't see my buckets

Check that your remote has endpoint set with https://, and add force_path_style = true. Without path-style, rclone may try bucket-prefixed hostnames.

s3cmd fails on bucket operations

Set both host_base and host_bucket to your endpoint hostname (no scheme) and use_https = True. A mismatch between those two values is the usual culprit.

Cyberduck shows certificate or host errors

Enter the endpoint hostname only (no https://) as the server, use your access key as the username and secret key as the password, and prefer path-style connect mode if offered.

My SDK uses virtual-host addressing and breaks

Force path-style. For boto3:

from botocore.config import Config
s3 = boto3.client("s3", endpoint_url="https://YOUR-ENDPOINT/",
                  config=Config(s3={"addressing_style": "path"}))

See Path-style vs virtual-host.

A tool demands a region and won't proceed

Enter us-east-1. It's a placeholder; the endpoint URL determines routing.

A large download stalls partway

Retry — most clients resume from where they left off. Raising concurrency can also help. If a specific object consistently fails, contact support@clearstreamer.com.

My client tries to upload or create a bucket and fails

That's expected — ZenDRIVE S3 Access is read-only. Use list/download operations only; see Browsing & downloading.

My GUI client isn't listed here

If it supports a custom S3 endpoint plus access/secret keys and path-style addressing, it should work. Mirror the settings from the client examples.