INFRASTRUCTURE

What it needs

• S3-compatible object storage: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

PREREQUISITES

Before you start

• Authorized access to the Backblaze B2 S3 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

TESTED CONFIGURATION

Exactly what was tested

• build: npm run build --if-present
• install: npm install
• runtime: node
• size: s-1vcpu-1gb
• start: npm run start
• template: node-22

STEP BY STEP

How to do it

1. 1

Inventory the source

List what Backblaze B2 S3 bucket provides beyond the component you are moving. Out of scope here: B2 file versions, lifecycle rules and application-key restrictions are not migrated.

2. 2

Source step 1

Inventory the bucket with rclone size or the B2 dashboard

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

Source step 3

Verify a sample of objects by size and checksum after the copy

5. 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. 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/public-media-library).

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

Rollback

Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

EXAMPLES

Tested examples

• Express pattern fixture (destination) (tests/deploy-canaries/express-patterns): Verified destination basis: public media library.

SUCCESS CHECKS

How to know it worked

• destination app responds on its public URL (/ on the live URL, expect ample canary express patterns)
• public-media-library check from the destination example (/p/public-media-library on the live URL, expect see the pattern fixture checks)
• data or object counts and checksums match the source

LIMITATIONS

Know the limits

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Backblaze B2 S3 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: B2 file versions, lifecycle rules and application-key restrictions are not migrated.
• Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
• PutObject and GetObject with path-style addressing are verified; bulk copy tooling and other S3 operations are not.

COST

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• app server x1 s-1vcpu-1gb: 5.00 USD

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

EVIDENCE

Verification evidence

• canary_run on 2026-09-21T02:34:39Z at revision 1d28ae0-dirty (CLI 0.1.21): 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 object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly). The source-side export from Backblaze B2 S3 bucket is documented from the vendor's standard tooling and was not executed by this catalog's evidence. (expires 2027-03-20T02:34:39Z)

EXECUTION

Execution binding

No execution binding. This recipe is documentation only; nothing is executed automatically.

NEXT ACTIONS

Typed next actions

• Browse the catalog index (GET /v1/catalog on the api origin; authentication not required, approval not required)
• Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; authentication not required, approval not required)
• Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; authentication required, approval not required)
• Read the existing agent authentication setup (GET /mcp/setup on the api origin; authentication not required, approval not required)
• Browse Backblaze B2 S3 bucket (GET /v1/catalog/nodes/migration%3Abackblaze-b2-s3-bucket on the api origin; authentication not required, approval not required)
• Browse Public media library (GET /v1/catalog/nodes/pattern%3Apublic-media-library on the api origin; authentication not required, approval not required)
• Browse Migrate objects (GET /v1/catalog/nodes/intent%3Amigrate-objects on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.