### Migrate Supabase Storage bucket: Browser file uploads

Move object storage from Supabase Storage bucket to Ample, one component at a time. Destination verified on Ample: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

**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: Browser file uploads
- Where can I host Browser file uploads?
- I need a component-scoped export/import or reconfiguration procedure for Browser file uploads, 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

---

#### 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.
    ```bash
    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/browser-file-uploads).
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
- Browser-file-uploads 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.
- Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
- Verified: PutObject and GetObject with path-style addressing; bulk copy tooling and other S3 operations are not.

---

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $5.00
- **Basis**: Size prices from pricing.toml (loaded by the API)

#### Components
- App server: 1 x s-1vcpu-1gb = $5.00/month

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