## Migrate CloudFront Distribution: Versioned Static Assets

### Summary
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.

**Not migrated automatically:** CloudFront cache behaviors, Lambda@Edge and CloudFront Functions, signed URLs and custom TTLs 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, 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.

### Representative Queries
- Migrate CloudFront distribution: Versioned static assets  
- Where can I host Versioned static assets?  
- I need a component-scoped export/import or reconfiguration procedure for Versioned static assets, with compatibility checks, verification and rollback.

### Resource Requirements
- `primitive:cdn`

### Infrastructure Requirements
- **CDN:** The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store. (Status: verified)

### Migration Source
CloudFront distribution

### Execution Status
Unbound  
### Docs Only
True

### 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

### Workflow Steps
1. **Inventory the source:** List what CloudFront distribution provides beyond the component you are moving. Out of scope: CloudFront cache behaviors, Lambda@Edge and CloudFront Functions, signed URLs and custom TTLs.
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.
   ```bash
   ample bucket publish 
   ```
6. **Validate before cutover:** Run the app's own checks and, for data, compare counts and checksums.
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.

### Examples
- **Next.js pattern fixture (destination):** Verified destination basis: CDN delivery.
  - Source Ref: `tests/deploy-canaries/next-js-patterns`

### Success Checks
- Destination app responds on its public URL.
  - **Type:** http_get  
  - **Path:** `/`  
  - **Expect:** ample canary next js patterns

- Versioned static assets check from the destination example.
  - **Type:** http_get  
  - **Path:** `/p/versioned-static-assets`  
  - **Expect:** see the pattern fixture checks

- Data or object counts and checksums match the source.
  - **Type:** manual  
  - **Expect:** operator comparison before cutover

### Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from CloudFront distribution's standard tooling.
- No full source-product parity is claimed; certain elements are not migrated.

### Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** $5.00  
- **Basis:** size prices from pricing.toml at build revision.
  - **Component:** app server (size: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00)
  - **Note:** Destination always-on monthly price of the tested sizes; apps auto-pause when idle.

### Evidence Summary
- **Kind:** canary_run  
- **Summary:** Destination side verified: the Next.js pattern fixture deployed on Ample.
- **Observed At:** 2026-09-21T02:34:39Z

### Next Actions
- **Action:** Browse the catalog index.
- **Action:** Search published recipes by intent, stack and constraints.
- **Action:** Prepare a side-effect-free deployment plan for an authorized project.