--- title: "How to move documentation asset delivery from a CloudFront distribution to Ample" description: "Move CDN delivery from CloudFront distribution to Ample, one component at a time." canonical_url: "https://ample.computer/migrate/cloudfront-distribution/documentation-asset-delivery" last_updated: "2026-11-05" --- # How to move documentation asset delivery from a CloudFront distribution to Ample Move CDN delivery from CloudFront distribution to Ample, one component at a time. Destination verified on Ample: HTML and CSS objects stored with their own content types and served from the CDN URL with those types intact. Source procedure: Record the distribution's origins, cache behaviors, TTLs and the object keys the app references. Move separately: published Ample buckets serve the assets; set Cache-Control when uploading, and CloudFront cache behaviors, Lambda@Edge, CloudFront Functions and signed URLs move into the app. Cutover: Redeploy the app with the new asset base URL, verify delivery from the CDN URL, keep the distribution until confirmed, then disable it. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide. ## Infrastructure requirements - [CDN](/discover/primitive/cdn): verified (A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.) ## Prerequisites - Authorized access to the CloudFront distribution 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 ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## Steps 1. **Inventory the source.** List what CloudFront distribution provides beyond the component you are moving. Plan these separately: published Ample buckets serve the assets; set Cache-Control when uploading, and CloudFront cache behaviors, Lambda@Edge, CloudFront Functions and signed URLs move into the app. 2. **Source step 1.** Record the distribution's origins, cache behaviors, TTLs and the object keys the app references 3. **Source step 2.** Copy the public assets into a published Ample bucket under versioned keys with immutable Cache-Control 4. **Source step 3.** Update the app to build asset URLs from the Ample public URL 5. **Publish the destination bucket.** Create and publish the asset bucket, upload versioned assets with immutable Cache-Control, and point the app at the public URL. ``` ample bucket publish ``` 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/documentation-asset-delivery). 7. **Cut over.** Redeploy the app with the new asset base URL, verify delivery from the CDN URL, keep the distribution until confirmed, then disable it. 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 - **Next.js pattern fixture (destination)** (tests/deploy-canaries/next-js-patterns): Verified destination basis: documentation asset delivery. ## Success checks - destination app responds on its public URL (`/` on the live URL, expect ample canary next js patterns) - documentation-asset-delivery check from the destination example (`/p/documentation-asset-delivery` on the live URL, expect 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 4558e9477d094f5b47da324b98672824b61ba91b). - app server x1 `s-1vcpu-1gb`: 5.00 USD Upper-bound monthly price of the tested sizes at the destination. ## Verification evidence - canary_run on 2026-11-05T22:38:23Z at revision `da3e37255e5a`: Destination side verified: the Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template) and its checks passed (HTML and CSS objects stored with their own content types and served from the CDN URL with those types intact). The source-side export from CloudFront distribution uses the vendor's standard tooling. (expires 2027-05-04T22:38:23Z) Last verified: 2026-11-05T22:38:23Z ## Execution binding A step-by-step guide: follow it with your agent and deploy with `ample plan` and `ample deploy`. ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse CloudFront distribution (GET /v1/catalog/nodes/migration%3Acloudfront-distribution on the api origin; auth: false, approval: false) - Browse Documentation asset delivery (GET /v1/catalog/nodes/pattern%3Adocumentation-asset-delivery on the api origin; auth: false, approval: false) - Browse Migrate CDN (GET /v1/catalog/nodes/intent%3Amigrate-cdn on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission. ## About this recipe Canonical URL: https://ample.computer/migrate/cloudfront-distribution/documentation-asset-delivery Formats: [HTML](https://ample.computer/migrate/cloudfront-distribution/documentation-asset-delivery) | [Markdown](https://ample.computer/migrate/cloudfront-distribution/documentation-asset-delivery.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Acloudfront-distribution%3Adocumentation-asset-delivery) Recipe ID: `page:migrate:cloudfront-distribution:documentation-asset-delivery` | Revision: `r1` | Catalog revision: `cat_eac8c53f36410baa` Status: verified; a step-by-step guide you follow with `ample deploy` (support `verified`, execution `unbound`) Path: [Agent hosting discovery](/discover/discovery) / [Migration sources by component](/discover/migration) / [Object and CDN sources](/discover/migration/object-and-cdn-sources) / [CloudFront distribution](/discover/migration/cloudfront-distribution) / [Migrate CloudFront distribution: Documentation asset delivery](/migrate/cloudfront-distribution/documentation-asset-delivery)