Migrate Cloudflare CDN configuration: Cache policy by content · Ample Computer
Migration guide
Migrate Cloudflare CDN configuration: Cache policy by content
Move CDN delivery from Cloudflare CDN configuration to Ample, one component at a time. Destination verified on Ample: an immutable versioned asset and a mutable latest pointer stored with different Cache-Control headers in a published bucket, each served from the CDN URL with the header exactly as stored. Source procedure: Record page rules, cache rules and the asset paths the app references. Move separately: published Ample buckets serve the assets; set Cache-Control when uploading, and Cloudflare cache rules, Workers and Transform Rules move into the app. Cutover: Redeploy the app with the new asset base URL, verify delivery from the CDN URL, then retire the old cache rules. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.
Verified November 5, 2026
What it runs on
- CDNverified
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.
You need
- Authorized access to the Cloudflare CDN configuration 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
build npm run build --if-present
install npm install
runtime node
sizes-1vcpu-1gb
start npm run start
template node-22
Steps
Inventory the source. List what Cloudflare CDN configuration provides beyond the component you are moving. Plan these separately: published Ample buckets serve the assets; set Cache-Control when uploading, and Cloudflare cache rules, Workers and Transform Rules move into the app.
Source step 1. Record page rules, cache rules and the asset paths the app references
Source step 2. Copy the public assets into a published Ample bucket under versioned keys with immutable Cache-Control
Source step 3. Update the app to build asset URLs from the Ample public URL
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 <bucket-name>
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/cache-policy-by-content).
Cut over. Redeploy the app with the new asset base URL, verify delivery from the CDN URL, then retire the old cache rules.
Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.
How it was checked
✓ destination app responds on its public URL · http get/ → “ample canary next js patterns”
✓ cache-policy-by-content check from the destination example · http get/p/cache-policy-by-content → “see the pattern fixture checks”
✓ data or object counts and checksums match the source · manual → “operator comparison before cutover”
Evidence
- November 5, 2026 · canary run
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 (an immutable versioned asset and a mutable latest pointer stored with different Cache-Control headers in a published bucket, each served from the CDN URL with the header exactly as stored). The source-side export from Cloudflare CDN configuration uses the vendor's standard tooling.
Tested examples
- Next.js pattern fixture (destination). Verified destination basis: cache policy by content.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Cloudflare CDN configuration's standard tooling.
- Plan separately: published Ample buckets serve the assets; set Cache-Control when uploading, and Cloudflare cache rules, Workers and Transform Rules move into the app.
- Verified on the node-22 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API; copy objects with rclone or the AWS CLI in path-style mode.