How it works

What happens when my S3 client makes a request?

Your client signs each request with your access key and secret key (standard S3 signing), then sends it over HTTPS to your dedicated CDN node's endpoint. The node serves the request and returns the result — the same request/response flow you'd have with any S3 endpoint.

flowchart LR
    A[Your S3 client] -- HTTPS, signed --> B[Your dedicated CDN node]
    B -- S3 response --> A

Why route through a CDN node instead of connecting directly?

The dedicated node gives you a stable endpoint, a bandwidth tier reserved for your account, and a consistent network path. You get predictable performance rather than the variability of a shared public endpoint.

Is my traffic encrypted?

Yes. Connections use HTTPS/TLS, so data is encrypted in transit between your client and your node. See TLS & HTTPS.

Does my bandwidth tier limit every request?

Your tier sets the throughput ceiling for your node (for example, 1 Gbps). Individual transfers can use up to that ceiling; the limit is on sustained throughput, not on the number of requests or objects. See Understanding bandwidth.

What part is "dedicated"?

The CDN node serving your endpoint is reserved for your account. Your throughput allocation is yours — it isn't divided among other customers. See Dedicated CDN Node.

Do I manage the server?

No. ZenDRIVE S3 Access is a managed service — you interact with it purely through the S3 API and your endpoint URL. There's no operating system for you to patch or maintain.

What happens if my node has a problem?

Reach out to support@clearstreamer.com. Because the node is dedicated to your account, support can look at your specific service rather than a shared system.