# Host blog with Next.js: object-stored public media ## Summary Deploy a blog built with Next.js on Ample using the public media library pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on Next.js: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the blog-specific behavior as your application code. ## Infrastructure requirements - Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.) - Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.) - S3-compatible object storage: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.) - CDN: verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.) ## Prerequisites - A Next.js project that builds and starts with the documented commands (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template) - A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env) - A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*) - An Ample account token with servers:write, databases:read, buckets:read ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## Steps 1. **Build and start.** next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. The server must bind 0.0.0.0 on PORT. 2. **Implement the pattern on PostgreSQL.** The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Copy the approach into your schema; keep migrations idempotent and run them with --release-command. 3. **Wire object storage.** Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL. 4. **Deploy.** Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op. ``` ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=... ``` 5. **Verify.** Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`. ``` ample logs --kind build ``` ## Tested examples - **Next.js pattern fixture** (tests/deploy-canaries/next-js-patterns): Multi-pattern Next.js app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules. ## Success checks - app responds on its public URL (`/` on the live URL, expect ample canary next js patterns) - public-media-library self-test (`/p/public-media-library` on the live URL, expect a CDN URL whose content is served publicly) ## Limitations - Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Next.js major versions are not verified. - The blog itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified. - Region, compliance attestations and request-duration limits are unknown and not claimed. - Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature. - Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together. - PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not. - The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys). ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0-dirty (CLI 0.1.21)`: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for public-media-library and configuration-secrets. Pattern proof: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. (expires 2027-03-20T02:34:39Z) - canary_run on 2026-09-20T01:54:51Z at revision `199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)`: The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation. (expires 2027-03-19T01:54:51Z) Last verified: 2026-09-21T02:34:39Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-21T03:19:59.461917+00:00 at revision `49962bcade4f`, binding state `current`, required scopes: servers:write, databases:read, buckets:read.