Migrate Cloudflare CDN Configuration: Origin Cache Refresh

Move CDN delivery from Cloudflare CDN configuration to Ample, one component at a time. Destination verified on Ample: a no-cache object overwritten in the published bucket and the CDN URL serving the new content on the next fetch (refresh=ok before=v1 after=v2), verified by the app fetching its own public URL.

Migration Source

Source procedure: Record page rules, cache rules and the asset paths the app references. Not migrated automatically: Cloudflare cache rules, Workers, Transform Rules and tiered caching are not migrated; Ample verifies delivery of published bucket objects only.

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.

Prerequisites

• 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

Workload

Origin cache refresh

Workflow Steps

1. Inventory the source: List what Cloudflare CDN configuration provides beyond the component you are moving. Out of scope here: Cloudflare cache rules, Workers, Transform Rules and tiered caching are not migrated; Ample verifies delivery of published bucket objects only.
2. Source step 1: Record page rules, cache rules and the asset paths 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.
   Command: 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/origin-cache-refresh).
7. Cut over: Redeploy the app with the new asset base URL, verify delivery from the CDN URL, then retire the old cache rules.
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

Next.js Pattern Fixture (Destination)

• Verified destination basis: origin cache refresh.
• Source Reference: tests/deploy-canaries/next-js-patterns

Success Checks

1. Destination app responds on its public URL
   Kind: http_get
   Path: /
   Expectation: ample canary next js patterns
2. Origin-cache-refresh check from the destination example
   Kind: http_get
   Path: /p/origin-cache-refresh
   Expectation: see the pattern fixture checks
3. Data or object counts and checksums match the source
   Kind: manual
   Expectation: operator comparison before cutover

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Cloudflare CDN configuration'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: Cloudflare cache rules, Workers, Transform Rules and tiered caching are not migrated; Ample verifies delivery of published bucket objects only.
• 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
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Components

• Name: app server

  • Size: s-1vcpu-1gb
  • Quantity: 1.0
  • Monthly Amount: 5.0

• Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Evidence Summary

• Kind: canary_run
• Summary: 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 (a no-cache object overwritten in the published bucket and the CDN URL serving the new content on the next fetch).
• 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/origin-cache-refresh], destination only: true, template: node-22

Unknowns

• Region availability is unknown until a verified region fact is recorded
• Compliance attestations are unknown; none are claimed

Formats

• HTML: https://ample.computer/migrate/cloudflare-cdn-configuration/origin-cache-refresh
• Markdown: https://ample.computer/migrate/cloudflare-cdn-configuration/origin-cache-refresh.md
• JSON: https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Acloudflare-cdn-configuration%3Aorigin-cache-refresh

Next Actions

1. Browse the catalog index
   Action ID: browse-catalog
   Operation ID: catalog_index
   Method: GET
   Relative Path: /v1/catalog
   Requires Authentication: false

2. Search published recipes by intent, stack and constraints
   Action ID: search-recipes
   Operation ID: search_recipes
   Method: POST
   Relative Path: /v1/catalog/search
   Parameters: { limit: 5, query: "Migrate Cloudflare CDN configuration: Origin cache refresh" } Requires Authentication: false

3. Prepare a side-effect-free deployment plan for an authorized project
   Action ID: plan:page:migrate:cloudflare-cdn-configuration:origin-cache-refresh
   Operation ID: plan_deployment
   Method: POST
   Relative Path: /v1/catalog/plan
   Requires Authentication: true

4. Read the existing agent authentication setup
   Action ID: auth-setup
   Operation ID: existing_auth_setup
   Method: GET
   Relative Path: /mcp/setup
   Requires Authentication: false

5. Browse Cloudflare CDN configuration
   Action ID: browse:migration:cloudflare-cdn-configuration
   Operation ID: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/migration%3Acloudflare-cdn-configuration
   Requires Authentication: false

6. Browse Origin cache refresh
   Action ID: browse:pattern:origin-cache-refresh
   Operation ID: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/pattern%3Aorigin-cache-refresh
   Requires Authentication: false

7. Browse Migrate CDN
   Action ID: browse:intent:migrate-cdn
   Operation ID: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/intent%3Amigrate-cdn
   Requires Authentication: false