ZoophostDocs

Create and manage buckets

Buy a Z2 storage plan, create buckets, check capacity and upload files from the console or any S3 client.

Z2 Object Storage3 min read

Z2 Object Storage is S3-compatible storage on our own cluster. A storage plan gives you one pool of capacity, an S3 endpoint and one access key. You split the pool into as many buckets as you need.

Buy a storage plan

  1. Open zoophost.com/storage and pick a size: 100 GB, 500 GB or 1 TB.
  2. Check out. You can name the first bucket at checkout, or leave it blank and let one be generated.
  3. The plan appears in the console under Z2 Storage.

Bucket names must be 3–63 characters, lowercase letters, digits and hyphens. They start and end with a letter or digit, and they cannot be changed after creation.

The storage page

Console → Z2 Storage shows summary tiles:

  • Plans — active storage subscriptions
  • Stored — bytes used against total capacity
  • Buckets — bucket count

Each plan card shows the plan name, SKU, region, used of quota, utilization percentage, bucket/object counts and renewal date.

Capacity is one pool

Open the plan to see the Capacity card:

  • Stored — actual bytes across all buckets
  • Allocated to buckets — quota reserved per bucket
  • Unallocated — what is left

Per-bucket quotas do not add capacity. Every bucket is a slice of the same plan. A new bucket receives the remaining unallocated capacity as its hard quota, so leave at least 1 GiB free if you plan to add another bucket later.

Writes beyond a bucket's quota are refused. There is no overage charge.

Create a bucket

  1. Open the plan.
  2. In Buckets, choose New bucket.
  3. Enter the name.
  4. Choose Create bucket.

The bucket is available immediately in the Files card and through the S3 API.

Upload and browse files

The Files card is a small file browser:

  • Pick a bucket.
  • Upload files directly (single uploads up to 1 GB).
  • Navigate folders, download and delete objects.
  • Bulk delete accepts up to 1,000 keys, or a prefix ending in /.

For anything larger or automated, use the S3 API. See Connect with the AWS CLI.

Connection details

The Connection card holds what every S3 tool needs:

Field Use
Endpoint Base URL for API calls
Region Region name to pass to the SDK
Access key Show credentials reveals the Key ID and Secret

There is one key per storage plan, with owner rights on every bucket in it. Rotate key issues a new pair and immediately revokes the old one — every tool using the old key stops working until you update it.

Use the endpoint and region exactly as the console shows them. The quick-start tabs on the same card prefill AWS CLI, environment variable and boto3 examples.

Delete a bucket

Deleting a bucket from the console deletes every object inside it. That cannot be undone. If the data matters, copy it out first.

Bucket deletion is a console action, not an S3 operation. DeleteBucket through an S3 client returns an error by design.

Common uses

  • Backups — VPS and dedicated machines pushing restic or rclone archives.
  • Uploads — user files and media from an app, with presigned URLs.
  • Static assets — images, documents and exports served through your own app or a CDN.
  • Archives — logs and analytics data kept out of the database.

Next

  • z2
  • object storage
  • bucket
  • s3
  • capacity
  • upload

Ready to use this

S3-compatible buckets your existing tools already speak.

  • No egress fees
  • Per-bucket quotas from the console
See Z2 storage plans
Still stuck? Open a ticket from Support tickets in the console, or email [email protected]. Include the service name, the exact error and what you already tried.