# 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`. Not migrated automatically: Bucket policies, IAM conditions, lifecycle rules, versioning, replication and event notifications are not migrated; only PutObject and GetObject are verified on Ample. 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.

## Representative Queries
- Migrate Amazon S3 bucket: Private document library
- Where can I host Private document library?
- I need a component-scoped export/import or reconfiguration procedure for Private document library, with compatibility checks, verification and rollback.

## Requirements
### 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.

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

### Workflow Steps
1. **Inventory the source**: List what Amazon S3 bucket provides beyond the component you are moving. Out of scope here: Bucket policies, IAM conditions, lifecycle rules, versioning, replication and event notifications are not migrated; only PutObject and GetObject are verified on Ample.
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.
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/private-document-library).
7. **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.
8. **Rollback**: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Success Checks
- Destination app responds on its public URL
- Private-document-library 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: Bucket policies, IAM conditions, lifecycle rules, versioning, replication and event notifications are not migrated; only PutObject and GetObject are verified on Ample.
- Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.

## Cost Estimate
- **Monthly Amount**: $5.00 USD
- Basis: size prices from pricing.toml (loaded by the API)
- Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle.

## Examples
- **Express pattern fixture (destination)**: Verified destination basis: private document library.

## Evidence Summary
- Destination side verified: the Express pattern fixture deployed on Ample and its checks passed.

## 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 
- Read the existing agent authentication setup 
- Browse Amazon S3 bucket 
- Browse Private document library 
- Browse Migrate objects