Deliver public assets through CDN for NestJS · Ample Computer
Deliver public assets through CDN for NestJS
Cdn assets for a NestJS app on Ample. Verified on NestJS: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template.
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.CDNverified
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 NestJS project (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template)
- A bucket from
ample bucket createwith 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
Build and start. npm install, nest build (TypeScript) then node dist/main.js on the node-22 template; the server must bind 0.0.0.0 on PORT.
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.
$ ample bucket publish <bucket-name>Verify. Fetch the live URL and /p/versioned-static-assets on the example; on failure read the build and runtime logs.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary nestjs patterns”
✓ versioned-static-assets check from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”
Evidence
November 6, 2026 · canary run
NestJS pattern fixture deployed on Ample (npm install, nest build (TypeScript) then node dist/main.js 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
- NestJS pattern fixture. Verified CDN assets on NestJS.
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.