Migrate MinIO bucket: Bulk import staging · Ample Computer
Migrate MinIO bucket: Bulk import staging
Move object storage from MinIO 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 bucket with mc du or rclone size. Move separately: MinIO bucket policies, versioning, replication, ILM rules, and notifications are MinIO features; 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 MinIO 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
- S3-compatible object storage verified
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 MinIO 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-presentinstall npm installrun nodesizes-1vcpu-1gbstart npm run starttemplate node-22
Steps
Inventory the source. List what MinIO bucket provides beyond the component you are moving. Plan these separately: MinIO bucket policies, versioning, replication, ILM rules, and notifications are MinIO features; objects copy over the standard S3 API.
Source step 1. Inventory the bucket with
mc duorrclone sizeSource step 2. Copy objects with
mc mirrororrclone syncfrom MinIO 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/bulk-import-staging).
Cut over. Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep MinIO 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”
✓ 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
- 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 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)). The source-side export from MinIO bucket uses the vendor's standard tooling.
Tested examples
- Express pattern fixture (destination). Verified destination basis: bulk import staging.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample database, orample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use MinIO bucket's standard tooling.
- Plan separately: MinIO bucket policies, versioning, replication, ILM rules, and notifications are MinIO features; 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.