# Migrate Cloudflare R2 Bucket: Generated Downloads

Move object storage from Cloudflare R2 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 `rclone size` or the R2 dashboard. Not migrated automatically: R2 public buckets with custom domains, Workers bindings and lifecycle rules are not migrated; publish an Ample bucket for public assets instead.

**Cutover:** Switch the app's `S3_*` environment to the Ample bucket with a redeploy, verify reads and writes, keep R2 read-only until confirmed.

**Rollback:** Keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## Prerequisites
- Authorized access to the Cloudflare R2 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 Cloudflare R2 bucket provides beyond the component you are moving. Out of scope here: R2 public buckets with custom domains, Workers bindings and lifecycle rules are not migrated; publish an Ample bucket for public assets instead.

2. **Source step 1**  
   Inventory the bucket with `rclone size` or the R2 dashboard

3. **Source step 2**  
   Copy objects with `rclone sync` from the R2 S3-compatible endpoint 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.
   ```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/generated-downloads`).

7. **Cut over**  
   Switch the app's `S3_*` environment to the Ample bucket with a redeploy, verify reads and writes, keep R2 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.

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from Cloudflare R2 bucket's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- No full source-product parity is claimed: R2 public buckets with custom domains, Workers bindings and lifecycle rules are not migrated; publish an Ample bucket for public assets instead.
- 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.