## The short version 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). 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. --- ## What it needs - [S3-compatible object storage](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.) --- ## Before you start - 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 --- ## How to do it 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. ``` 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/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. --- ## Tested examples - **Express pattern fixture (destination)** (`tests/deploy-canaries/express-patterns`): Verified destination basis: browser file uploads. --- ## How to know it worked - Destination app responds on its public URL (`/` on the live URL, expect ample canary express patterns) - Browser-file-uploads check from the destination example (`/p/browser-file-uploads` on the live URL, expect to see the pattern fixture checks) - Data or object counts and checksums match the source --- ## Cost estimate Estimated 5.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a). - App server x1 `s-1vcpu-1gb`: 5.00 USD Upper-bound monthly price of the tested sizes at the destination. Source costs are unknown to Ample. --- ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: 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 (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)). 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. (expires 2027-03-20T02:34:39Z) --- ## Execution binding No execution binding. This recipe is documentation only; nothing is executed automatically. --- ## Typed next actions - Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required) - Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required) - Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required) - Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required) - Browse Amazon S3 bucket (`GET /v1/catalog/nodes/migration%3Aamazon-s3-bucket` on the api origin; authentication not required, approval not required) - Browse Browser file uploads (`GET /v1/catalog/nodes/pattern%3Abrowser-file-uploads` on the api origin; authentication not required, approval not required) - Browse Migrate objects (`GET /v1/catalog/nodes/intent%3Amigrate-objects` on the api origin; authentication not required, approval not required) Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client. --- ## Identifiers and status Recipe `page:migrate:amazon-s3-bucket:browser-file-uploads`. Revision r1. Release **published** support **verified** execution **unbound** Formats: [HTML](/content/migrate/amazon-s3-bucket/browser-file-uploads/index.html) | [Markdown](/content/migrate/amazon-s3-bucket/browser-file-uploads.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Aamazon-s3-bucket%3Abrowser-file-uploads)