Migrate Cloudflare R2 Bucket: Browser File Uploads

Summary

Move object storage from Cloudflare R2 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 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.

Migration Source

Cloudflare R2 bucket

Workload

Browser file uploads

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

Steps to Migrate

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.

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

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.
• 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.
• 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)
  • Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Evidence Summary

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

Next Actions

• Browse the catalog index - GET /v1/catalog
• Search published recipes by intent - POST /v1/catalog/search
• Prepare a side-effect-free deployment plan - POST /v1/catalog/plan
• Read the existing agent authentication setup - GET /mcp/setup
• Browse Cloudflare R2 bucket - GET /v1/catalog/nodes/migration%3Acloudflare-r2-bucket
• Browse Browser file uploads - GET /v1/catalog/nodes/pattern%3Abrowser-file-uploads
• Browse Migrate objects - GET /v1/catalog/nodes/intent%3Amigrate-objects

References

• HTML Documentation
• Markdown Documentation
• JSON API