Migrate Amazon S3 bucket: Tenant-scoped object prefixes · Ample Computer

Migrate Amazon S3 bucket: Tenant-scoped object prefixes

Move object storage from Amazon S3 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 bucket (object count, total size, prefixes, largest objects) with aws s3 ls --recursive --summarize. Move separately: bucket policies, IAM conditions, lifecycle rules, versioning, replication and event notifications move into the app or are dropped; 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 the source bucket 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 Amazon S3 bucket provides beyond the component you are moving. Plan these separately: bucket policies, IAM conditions, lifecycle rules, versioning, replication and event notifications move into the app or are dropped; objects copy over the standard S3 API.

  2. Source step 1. Inventory the bucket (object count, total size, prefixes, largest objects) with aws s3 ls --recursive --summarize

  3. Source step 2. Copy objects with rclone sync or aws s3 sync from the S3 bucket 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/tenant-scoped-object-prefixes).

  2. Cut over. Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep the source bucket 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”
✓ tenant-scoped-object-prefixes check from the destination example · http get/p/tenant-scoped-object-prefixes → “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 (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 Amazon S3 bucket uses the vendor's standard tooling.

Tested examples

What it doesn’t cover