Storage Zone access and replication
Control how teams reach your Storage Zone, and decide where replicas live for durability and latency.
Connection model
- S3-compatible storage colocated with CDN edge for low-latency reads.
- Per-zone connection details (hostname, connection type, port) are revealed after creation and can be copied from the dashboard.
- Use the provided FTP access for simple uploads during beta; S3-compatible access is planned.
FTP users
- Create FTP users per Storage Zone; usernames default to generated ULIDs and can be customized.
- Passwords are stored hashed; rotate credentials by editing or deleting a user without touching stored objects.
- Use separate FTP users for automation vs. manual uploads to keep auditability straightforward.
Replication
- Admin-managed replication to EU targets (Nuremberg and Helsinki today). Ask the team to enable regions for your tenant.
- Use replication when you need:
- Higher durability and multi-site recovery.
- Lower latency for EU visitors outside the primary
eu-centralregion.
- Replication settings live on the Replication tab and are multi-select to allow fan-out when available.
Operational tips
- Keep bucket names stable; they cannot be changed after creation.
- For heavy ingestion, stage writes in one region and let replication fan out instead of uploading from multiple clients at once.