# Deliver public assets through CDN for ASP.NET Core

Cdn assets for a ASP.NET Core app on Ample. Verified on ASP.NET Core: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: `dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to PORT.

**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 ASP.NET Core project (`dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to PORT)
- 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`  
  `dotnet publish -c Release -o out`
- `runtime`  
  `dotnet`
- `sizes`  
  `1vcpu-1gb`
- `start`  
  `ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll`
- `template`  
  `dotnet-10`

## Steps

1. **Build and start.**  
   `dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to PORT; 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.
   
   ```
   $ 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.
   
   ```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL · `http get /` → “ample canary asp net core 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
   
   ASP.NET Core pattern fixture deployed on Ample (`dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to PORT); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

## Tested examples

- **ASP.NET Core pattern fixture.**  
  Verified CDN assets on ASP.NET Core.

## What it doesn’t cover

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