S3 clients¶
ZERO-Z3 speaks S3v4 and the IAM API, so any S3 client works. Access keys come from the customer portal; your bucket already exists, it was created with your order.
| Region | Region name | Endpoint |
|---|---|---|
| Frankfurt (FRA1) | zero-fra1 |
https://fra1.s3.zeroservices.eu |
| Frankfurt (FRA2) | zero-fra2 |
https://fra.s3.zeroservices.eu |
| Eygelshoven, Netherlands (EYL1) | zero-eyl1 |
https://eyl1.s3.zeroservices.eu |
Endpoints are path-style. Use the region name wherever a client asks for one.
Setup guides¶
| Tool | Typical use |
|---|---|
| AWS CLI | scripting, bucket policies, IAM users and keys |
| MinIO Client (mc) | day-to-day copy and mirror, presigned links, public access |
| rclone | sync and mount, native ZeroServices provider since 1.75 |
| Python (boto3) | applications, presigned URLs, multipart uploads |
| restic | encrypted, deduplicated backups |
| TrueNAS | cloud sync tasks from a NAS |
| Cyberduck | desktop client with ready-made ZERO-Z3 profiles |
| Veeam Backup & Replication | immutable backup repository |
Browsing without a client¶
The customer portal has an object browser: list, upload, download and delete objects, create and revoke access keys, configure custom domains with automatic TLS, CORS rules, static website hosting and geofencing (country-level allow and deny lists).
Users and keys (IAM)¶
Additional users and keys need no ticket; the AWS CLI guide shows the commands.
Public access and CORS¶
Public read access is a bucket policy (AWS CLI) or
one mc anonymous command (MinIO Client).
Buckets with static website hosting enabled answer with permissive CORS headers:
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, HEAD, OPTIONS
Access-Control-Allow-Headers: *
Access-Control-Max-Age: 600
Custom CORS rules (up to 10, with per-origin methods, headers and max-age) are set in the customer portal.
Quota on new accounts¶
New accounts start with a 1 TB quota that is lifted automatically after 60 days. Need it lifted earlier? Open a ticket.