# Migrate MinIO bucket: Public media library

Move object storage from MinIO bucket to Ample, one component at a time. Destination verified on Ample: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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.

## Workload
Public media library

## Migration Source
MinIO bucket

## Prerequisites
- 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

## Resource Requirements
- **primitive:s3-compatible-object-storage**

## Infrastructure Requirements
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## 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/public-media-library).
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: public media library.

## Success Checks
- Destination app responds on its public URL: **http_get** `/` expect: ample canary express patterns.
- Public-media-library check from the destination example: **http_get** `/p/public-media-library` expect: see the pattern fixture checks.
- Data or object counts and checksums match the source: **manual** expect: operator comparison before cutover.

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from MinIO bucket's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- No full source-product parity is claimed: MinIO bucket policies, versioning, replication, ILM rules and notifications are not migrated.
- Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
- PutObject and GetObject with path-style addressing are verified; bulk copy tooling and other S3 operations are not.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 5.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - **app server**: size `s-1vcpu-1gb`, quantity 1.0, monthly amount 5.0.
- **Note**: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

## Evidence Summary
- **Canary Run**: Destination side verified: the Express pattern fixture deployed on Ample and its checks passed. The source-side export from MinIO bucket is documented from the vendor's standard tooling and was not executed by this catalog's evidence.

## Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack, and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**
5. **Browse MinIO bucket**
6. **Browse Public media library**
7. **Browse Migrate objects**