# Migrate Amazon S3 bucket: Generated downloads

Move object storage from Amazon S3 bucket to Ample, one component at a time. Destination verified on Ample: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

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: Generated downloads  
- Where can I host Generated downloads?  
- I need a component-scoped export/import or reconfiguration procedure for Generated downloads, with compatibility checks, verification and rollback.

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

## Workload
- Generated downloads

## Migration Source
- Amazon S3 bucket

## 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/generated-downloads).
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: generated downloads.  
  Source Ref: `tests/deploy-canaries/express-patterns`

## 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
- **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, monthlyAmount: 5.0 
- **Note**: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

## Success Checks
- **destination app responds on its public URL**: Path: `/`, Expect: ample canary express patterns  
- **generated-downloads check from the destination example**: Path: `/p/generated-downloads`, Expect: see the pattern fixture checks  
- **data or object counts and checksums match the source**: Manual check; Expect: operator comparison before cutover.

## Evidence Summary
- **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 (an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3)). The source-side export from Amazon S3 bucket is documented from the vendor's standard tooling and was not executed by this catalog's evidence.

### Observed At
- 2026-09-21T02:34:39Z 
### Implementation Revision
- 1d28ae0-dirty (CLI 0.1.21) 
### Expires At
- 2027-03-20T02:34:39Z 
### Scope
- Checks: `/p/generated-downloads` 
- Destination Only: true  
- Template: node-22