Migrate CloudFront distribution: Versioned static assets · Ample Computer

Migrate CloudFront distribution: Versioned static assets

Move CDN delivery from CloudFront distribution to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. 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.

Verified November 5, 2026

What it runs on

You need

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

  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 <bucket-name>
  1. 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/versioned-static-assets).

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

  3. 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”
✓ versioned-static-assets check from the destination example· http get/p/versioned-static-assets → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

Evidence

  1. 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 (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from CloudFront distribution uses the vendor's standard tooling.

Tested examples

What it doesn’t cover