Migrate Supabase Storage bucket: Public media library · Ample Computer

Migrate Supabase Storage bucket: Public media library

Move object storage from Supabase Storage bucket to Ample, one component at a time. Destination verified on Ample: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Source procedure: Inventory objects through the Supabase Storage API or dashboard. Move separately: enforce authorization in the app and stream private objects through it; signed uploads use ample bucket upload-url, and image transformations move into the app. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep Supabase Storage read-only until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build npm run build --if-present
install npm install
runtime node
sizes - 1vcpu - 1gb
start npm run start
template node - 22

Steps

  1. Inventory the source. List what Supabase Storage bucket provides beyond the component you are moving. Plan these separately: enforce authorization in the app and stream private objects through it; signed uploads use ample bucket upload-url, and image transformations move into the app.

  2. Source step 1. Inventory objects through the Supabase Storage API or dashboard.

  3. Source step 2. Copy objects with rclone sync from the Supabase S3-compatible endpoint (or a scripted download) to the Ample bucket endpoint using the issued credentials.

  4. Source step 3. Verify a sample of objects by size and checksum after the copy.

  5. Create the destination bucket and copy. Create the bucket, copy with rclone or the S3 CLI in path-style mode using the issued credentials, then pass the credentials to the app as encrypted S3_* variables.

   $ ample bucket create --name <bucket-name>
  1. Validate before cutover. Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/public-media-library).

  2. Cut over. Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep Supabase Storage read-only until confirmed.

  3. Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

How it was checked

✓ destination app responds on its public URL · http get/ → “ample canary express patterns”
✓ public-media-library check from the destination example · http get/p/public-media-library → “see the pattern fixture checks”
✓ data or object counts and checksums match the source · manual → “operator comparison before cutover”

Evidence

  1. November 5, 2026 · canary run

Destination side verified: the Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start on the node-22 template) and its checks passed (an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly). The source-side export from Supabase Storage bucket uses the vendor's standard tooling.

Tested examples

What it doesn’t cover