Migrate DigitalOcean Spaces bucket: Bulk import staging · Ample Computer

Migrate DigitalOcean Spaces bucket: Bulk import staging

Move object storage from DigitalOcean Spaces bucket to Ample, one component at a time. Destination verified on Ample: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Source procedure: Inventory the Space with rclone size or s3cmd du. Move separately: publish an Ample bucket for public delivery; Spaces CDN settings, CORS rules and per-object ACLs move into the app. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep the Space 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 DigitalOcean Spaces bucket provides beyond the component you are moving. Plan these separately: publish an Ample bucket for public delivery; Spaces CDN settings, CORS rules and per-object ACLs move into the app.

  2. Source step 1. Inventory the Space with rclone size or s3cmd du

  3. Source step 2. Copy objects with rclone sync from the Spaces 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>
  1. 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/bulk-import-staging).

  2. Cut over. Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep the Space read-only until confirmed.

  3. 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”
✓ bulk-import-staging check from the destination example· http get/p/bulk-import-staging → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

Evidence

Tested examples

What it doesn’t cover