Migrate DigitalOcean Spaces bucket: Tenant-scoped object prefixes · Ample Computer

Migration guide

Migrate DigitalOcean Spaces bucket: Tenant-scoped object prefixes

Move object storage from DigitalOcean Spaces bucket to Ample, one component at a time. Destination verified on Ample: every tenant's objects stored under tenants// in a private bucket with an ownership row per object, reads refused for keys outside the caller's prefix or not owned (cross=forbidden), and a prefix-bound listing returning only that tenant's objects (own=1). 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

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.

    Example command:

    $ 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/tenant-scoped-object-prefixes).

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

  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

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 (every tenant's objects stored under tenants// in a private bucket with an ownership row per object, reads refused for keys outside the caller's prefix or not owned (cross=forbidden), and a prefix-bound listing returning only that tenant's objects (own=1)). The source-side export from DigitalOcean Spaces bucket uses the vendor's standard tooling.

Tested examples

What it doesn’t cover