Migrate Amazon S3 bucket: Private document library · Ample Computer
Migrate Amazon S3 bucket: Private document library
Move object storage from Amazon S3 bucket to Ample, one component at a time. Destination verified on Ample: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). 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.
What it runs on
- S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
- Authorized access to the Amazon 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
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
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.
Source step 1. Inventory the bucket (object count, total size, prefixes, largest objects) with
aws s3 ls --recursive --summarizeSource step 2. Copy objects with
rclone syncoraws s3 syncfrom the S3 bucket to the Ample bucket endpoint using the issued credentials (path-style)Source step 3. Verify a sample of objects by size and checksum after the copy
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>
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/private-document-library).
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.
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”
✓ private-document-library check from the destination example· http get/p/private-document-library → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”
Evidence
- 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 (a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok)). The source-side export from Amazon S3 bucket uses the vendor's standard tooling.
Tested examples
- Express pattern fixture (destination). Verified destination basis: private document library.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Amazon S3 bucket's standard tooling.
- Plan 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.
- 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.