Migrate Supabase Storage bucket: Generated downloads

Move object storage from Supabase Storage bucket to Ample, one component at a time. Destination verified on Ample: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Source procedure: Inventory objects through the Supabase Storage API or dashboard. Not migrated automatically: Supabase Storage RLS policies, signed URLs, and image transformations are not migrated; enforce authorization in the app and stream private objects through it. 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.

Representative Queries

• Migrate Supabase Storage bucket: Generated downloads
• Where can I host Generated downloads?
• I need a component-scoped export/import or reconfiguration procedure for Generated downloads, with compatibility checks, verification, and rollback.

Prerequisites

• Authorized access to the Supabase Storage bucket source and its export tooling
• An inventory of every component in scope and out of scope
• A validated backup or copy before any cutover
• An Ample account token with servers:write, buckets:write

Workload

Generated downloads

Migration Source

Supabase Storage bucket

Workflow Steps

1. Inventory the source
   List what Supabase Storage bucket provides beyond the component you are moving. Out of scope here: Supabase Storage RLS policies, signed URLs, and image transformations are not migrated; enforce authorization in the app and stream private objects through it.

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>
   

6. 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/generated-downloads).

7. 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.

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

Success Checks

• Destination app responds on its public URL.
• Generated-downloads check from the destination example.
• Data or object counts and checksums match the source.

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Supabase Storage bucket's standard tooling and was not executed in this catalog's evidence.
• No full source-product parity is claimed: Supabase Storage RLS policies, signed URLs, and image transformations are not migrated; enforce authorization in the app and stream private objects through it.

Cost Estimate

Monthly amount: $5.00 USD

• Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.