# Migrate Amazon S3 bucket: Browser file uploads

Move object storage from Amazon S3 bucket to Ample, one component at a time. Destination verified on Ample: content-type and size validation that rejects disallowed files, an object written to a private bucket, and a row linking the record to the object key (reject=ok upload=ok linked=ok).

## Summary
1. **Source Procedure:** Inventory the bucket (object count, total size, prefixes, largest objects) with `aws s3 ls --recursive --summarize`.  
2. **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.  
3. **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.  
4. **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: Browser file uploads  
- Where can I host Browser file uploads?  
- I need a component-scoped export/import or reconfiguration procedure for Browser file uploads, with compatibility checks, verification, and rollback.

## 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.  
   Command: `ample bucket create --name <bucket-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/browser-file-uploads).  
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.

## Examples
- **Express pattern fixture (destination)**  
   Verified destination basis: browser file uploads.

## Success Checks
- Destination app responds on its public URL (expect: "ample canary express patterns").  
- Browser-file-uploads check from the destination example (expect: see the pattern fixture checks).  
- Data or object counts and checksums match the source (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 Amazon S3 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: 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.  
- PutObject and GetObject with path-style addressing are verified; bulk copy tooling and other S3 operations are not.

## Cost Estimate
- **Monthly Amount:** $5.00 (USD)  
- Components:  
   - App server (size: s-1vcpu-1gb, quantity: 1.0) - $5.00.  
- Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.