page:recipes:approval workflow:next js:report exports

Host approval workflow with Next.js: downloadable reports

Deploy a approval workflow built with Next.js on Ample using the generated downloads 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. Verified on Next.js: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the approval workflow-specific behavior as your application code.

Representative Queries

• Host approval workflow with Next.js: downloadable reports
• Where can I host Approval workflow built with Next.js?
• I need an export query, generated artifact retention and authorized download flow.

Resource Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.
• Postgres: 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: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

Workflow 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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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.
4. Deploy
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks.

Examples

• Next.js pattern fixture: Multi-pattern Next.js app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL (expect: ample canary next js patterns).
• Generated-downloads self-test (expect: export=ok rows=3).

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.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Basis: Size prices from pricing.toml at build revision.
• Components:
  • App server: s-1vcpu-1gb - $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb - $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Next.js pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
• The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation.