# Deliver public assets through CDN for Hono

Cdn assets for a Hono app on Ample. Verified on Hono: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: npm install and npm run start with @hono/node-server on the node-22 template.

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

- A Hono project (npm install and npm run start with @hono/node-server on the node-22 template)
- 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** npm run build --if-present  
- **install** npm install  
- **runtime** node  
- **sizes** 1vcpu-1gb  
- **start** npm run start  
- **template** node-22

## Steps

1. **Build and start.** npm install and npm run start with @hono/node-server on the node-22 template; 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 hono 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  
Hono pattern fixture deployed on Ample (npm install and npm run start with @hono/node-server on the node-22 template); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

## Tested examples

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

## What it doesn’t cover

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