### Migrate MinIO bucket: Generated downloads

#### Summary
Move object storage from MinIO 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 the bucket with `mc du` or `rclone size`. Not migrated automatically: MinIO bucket policies, versioning, replication, ILM rules, and notifications are not migrated. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep MinIO read-only until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

#### Resource Requirements
- **S3-compatible object storage**

#### Migration Source
- **MinIO bucket**

#### Workload
- **Generated downloads**

#### Prerequisites
1. Authorized access to the MinIO bucket source and its export tooling
2. An inventory of every component in scope and out of scope
3. A validated backup or copy before any cutover
4. An Ample account token with servers:write, buckets:write

#### Workflow Steps
1. **Inventory the source**  
   List what MinIO bucket provides beyond the component you are moving. Out of scope here: MinIO bucket policies, versioning, replication, ILM rules, and notifications are not migrated.
2. **Source step 1**  
   Inventory the bucket with `mc du` or `rclone size`
3. **Source step 2**  
   Copy objects with `mc mirror` or `rclone sync` from MinIO to the Ample bucket endpoint using the issued credentials (path-style)
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.
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 MinIO 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 matches expectations. 
- 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.

#### Cost Estimate
- **Monthly Amount**: $5.00 USD
- **Basis**: Size prices from pricing.toml.

#### Evidence Summary
- Destination side verified: the Express pattern fixture deployed on Ample.