Endpoint & credentials¶
What do I need to connect?¶
Three values, all delivered in your welcome email:
| Value | Looks like | Used for |
|---|---|---|
| Access key | a short identifier | identifies your account |
| Secret key | a longer secret string | signs your requests (keep private) |
| Endpoint URL | https://your-node-hostname/ |
where the client connects |
Where do I find these?¶
In the welcome email sent when your service is provisioned. You can also have it resent from the client area, or ask support@clearstreamer.com.
Do I have to whitelist my IP first?¶
Yes — this is required. Your endpoint only accepts connections from a single IP address that you set as your whitelist IP in the client area. Until it's set, every connection is refused; if your public IP later changes, update it or you'll be locked out. Only that one IP can access your service at a time. You can change it from the client area or via the API — see Updating your whitelist IP and Access & data handling.
What format is the endpoint URL?¶
It's an HTTPS URL pointing at your dedicated node, for example
https://your-node-hostname/. Always include https://, and when a tool asks for a
host without the scheme, supply the hostname only.
My client asks for a "region" — what do I enter?¶
ZenDRIVE S3 Access doesn't require an AWS region. If your client insists on one, enter
us-east-1 as a harmless placeholder. The endpoint URL is what actually routes your
requests.
Should I use path-style or virtual-host addressing?¶
Use path-style (https://endpoint/bucket/key). It's the most compatible choice for
a dedicated S3 endpoint. Details and per-client flags are on
Path-style vs virtual-host.
Do I need any special ports or firewall rules?¶
Just outbound HTTPS (port 443) to your endpoint. No other ports are required.
How do I test that my credentials work?¶
List your buckets — if it returns without an authorization error, you're set:
aws --endpoint-url "https://YOUR-ENDPOINT/" s3 ls
If it fails, see connection errors.
Can I have more than one set of keys?¶
Each service comes with its own credentials. If you need key rotation or separate credentials for different systems, see Credentials & rotation.