# Deliver public assets through CDN for Echo

Cdn assets for a Echo app on Ample. Verified on Echo: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: `CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build).

**Verified**  November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [CDNverified](/content/discover/primitive/cdn/index.html)  
  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

- An Echo project (`CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build))
- A bucket from `ample bucket create` with credentials passed as encrypted `S3_*` environment variables
- An Ample account token with `servers:write`, `buckets:read`

## Exact tested configuration

- build: `CGO_ENABLED=0 go build -o app ./...`
- runtime: `go`
- sizes: `1vcpu-1gb`
- start: `./app`
- template: `ubuntu-24.04`

## Steps

1. **Build and start.** `CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build); the server must bind `0.0.0.0` on PORT.

2. **Publish a bucket for public assets.** Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.
   
   ```sh
   $ ample bucket publish <bucket-name>
   ```

3. **Verify.** Fetch the live URL and `/p/versioned-static-assets` on the example; on failure read the build and runtime logs.
   
   ```sh
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· `http get /` → “ample canary echo patterns”  
✓ versioned-static-assets check from the example· `http get /p/versioned-static-assets` → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
   Echo pattern fixture deployed on Ample (`CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build)); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

## Tested examples

- **Echo pattern fixture.** Verified CDN assets on Echo.

## What it doesn’t cover

- Verified on the ubuntu-24.04 template at `s-1vcpu-1gb`.
- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.
