# Migrate MinIO bucket: Tenant-scoped object prefixes

Move object storage from MinIO 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 with `mc du` or `rclone size`. Not migrated automatically: MinIO bucket policies, versioning, replication, ILM rules and notifications are not migrated. 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.

## Representative Queries
- Migrate MinIO bucket: Tenant-scoped object prefixes
- Where can I host Tenant-scoped object prefixes?
- I need a component-scoped export/import or reconfiguration procedure for Tenant-scoped object prefixes, with compatibility checks, verification and rollback.

## Resource Requirements
- S3-compatible object storage

## Workflow Steps
1. **Inventory the source**  
   List what MinIO bucket provides beyond the component you are moving. Out of scope here: MinIO bucket policies, versioning, replication, ILM rules and notifications are not migrated.
2. **Source step 1**  
   Inventory the bucket with `mc du` or `rclone size`.
3. **Source step 2**  
   Copy objects with `mc mirror` or `rclone sync` from MinIO 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.  
   Command: `ample bucket create --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 MinIO 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.

## Examples
- **Express pattern fixture (destination)**  
  Verified destination basis: tenant-scoped object prefixes.

## Success Checks
- Destination app responds on its public URL.
- Tenant-scoped-object-prefixes check from the destination example.
- Data or object counts and checksums match the source.

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- No full source-product parity is claimed: MinIO bucket policies, versioning, replication, ILM rules and notifications are not migrated.

## Cost Estimate
- Currency: USD
- Monthly Amount: $5.00

## Evidence Summary
- Destination side verified: The Express pattern fixture deployed on Ample and its checks passed (every tenant's objects stored under `tenants//` in a private bucket).

## Last Verified At
- 2026-09-21T02:34:39Z

## Next Actions
- Browse the catalog index.
- Search published recipes by intent, stack and constraints.
- Prepare a side-effect-free deployment plan for an authorized project.