Migrate Backblaze B2 S3 bucket: Generated downloads · Ample Computer

Migrate Backblaze B2 S3 bucket: Generated downloads

Move object storage from Backblaze B2 S3 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 B2 dashboard. Move separately: B2 file versions, lifecycle rules and application-key restrictions are B2 features; objects copy over the standard S3 API. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep B2 read-only until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build npm run build --if-present install npm install runtime node sizes-1vcpu-1gb start npm run start template node-22

Steps

  1. Inventory the source. List what Backblaze B2 S3 bucket provides beyond the component you are moving. Plan these separately: B2 file versions, lifecycle rules and application-key restrictions are B2 features; objects copy over the standard S3 API.

  2. Source step 1. Inventory the bucket with rclone size or the B2 dashboard

  3. Source step 2. Copy objects with rclone sync from the B2 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.

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

## How it was checked

✓ destination app responds on its public URL · http get/ → “ample canary express patterns”  
✓ generated-downloads check from the destination example · http get/p/generated-downloads → “see the pattern fixture checks”  
✓ data or object counts and checksums match the source · manual → “operator comparison before cutover”

## Evidence

1. November 5, 2026 · canary run

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 (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)). The source-side export from Backblaze B2 S3 bucket uses the vendor's standard tooling.

## Tested examples

- **Express pattern fixture (destination).** Verified destination basis: generated downloads.

## What it doesn’t cover

- A step-by-step guide: each stage is an ordinary `ample deploy`, `ample database` or `ample bucket` command you run.
- The destination side was verified on Ample with the pattern fixture; the source-side steps use Backblaze B2 S3 bucket's standard tooling.
- Plan separately: B2 file versions, lifecycle rules and application-key restrictions are B2 features; objects copy over the standard S3 API.
- Verified on the node-22 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API; copy objects with rclone or the AWS CLI in path-style mode.