Creating buckets

/tools/cloud-storage → Buckets → New bucket.

Fields

• Name — globally unique within Suzko Cloud Storage. Lowercase letters, numbers, hyphens. 3–63 chars.
• Region — auto (recommended; we pick the lowest-latency edge based on access patterns). Or pin to a specific region.
• Public access — off by default. Toggle on for buckets that serve content directly (static site assets, public uploads).

Public vs private

• Private — every read requires a signed URL or authenticated request. Use for anything sensitive.
• Public — objects readable by anyone with the URL. Use for CDN-style asset hosting.

Toggle public access per bucket in Bucket → Settings → Public access. Existing objects' permissions update on the next read.

CORS

By default, buckets allow GET requests from anywhere when public. For cross-origin uploads (PUT/POST from a browser), add a CORS policy:

Bucket → CORS → Add rule. Example for upload-from-browser:

{
  "AllowedOrigins": ["https://yoursite.com"],
  "AllowedMethods": ["GET", "PUT", "POST"],
  "AllowedHeaders": ["*"],
  "ExposeHeaders": ["ETag"],
  "MaxAgeSeconds": 3000
}

Custom domain

For public buckets, you can attach a custom domain (e.g. cdn.yourdomain.com) instead of using yourbucket.storage.suzko.net.

Bucket → Custom domain → add the domain → set a CNAME at your DNS pointing to the value shown. We issue the TLS cert automatically.

Deleting

Bucket → Delete bucket. Must be empty first — use the bulk- delete UI or your S3 client to clear it.