Object Storage · Public access
Docs / Object Storage

Public access

Public-read buckets serve objects to anyone with the URL, optionally through a custom domain or as a static website.

A Public read bucket serves its objects to anyone with the object's URL — no credentials needed. A Private bucket (the default) requires either a signed request from an access key, or a short-lived presigned link generated from the console or API.

Public URLs

Once a bucket is Public read, any object in it is reachable at a path built from the bucket's endpoint, its name, and the object's key. The console's Files tab shows a Copy public URL action on each object in a public bucket — use that rather than constructing the URL by hand.

text
 
Important
Switching a bucket to Public read requires a payment method on file — add a card under Billing first if you haven't already.

Custom domain

Serve a public bucket's objects from your own domain instead of the platform's. Available on Public read buckets only, from the bucket's Settings tab.

  1. 1
    Point DNS at the platform first
    Add an A record for your domain pointing at the address shown in Settings, before connecting it — the certificate step below depends on DNS already resolving.
  2. 2
    Enter your domain and connect
    Type the domain (e.g. assets.example.com) into the Custom domain field and click Connect. This automatically requests a TLS certificate for it.
  3. 3
    Wait for it to go live
    If DNS was already pointed correctly, the domain is live over HTTPS within moments. If the certificate request fails because DNS hasn't propagated yet, the domain still serves over plain HTTP in the meantime — retry once DNS has caught up.
Note
A custom domain only serves anonymous public reads — it can't be used for signed/authenticated S3 requests (uploads, deletes, or access to a private bucket). Use the platform's own endpoint with your access key for those.
Bucket Settings tab showing CORS rules, a Custom domain section, and the Danger Zone delete-bucket control
Custom domain, CORS rules, and the Danger Zone all live further down the same Settings tab.

Static website hosting

Turn on Static website hosting in a bucket's Settings tab to serve it as a simple static site — set an index document (defaults to index.html) and the bucket serves that file at its root, the way any static-site host would.