Host graphql api with NestJS: stored input and output artifacts · Ample Computer

Host graphql api with NestJS: stored input and output artifacts

Deploy a GraphQL API built with NestJS 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 NestJS: 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). The GraphQL API-specific behavior (your export formats, retention policy and entitlement model) is your application code on that verified basis.

What it runs on

You need

Exact tested configuration

Steps

  1. 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.

  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 needs an answer first). Re-running with no change is a no-op.

    $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
    ```

5. **Verify.** Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```sh
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary nestjs patterns”  
✓ generated-downloads self-test · http get/p/generated-downloads → “export=ok rows=3 (with ?token=...; 401 without)”

## Evidence

1. 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); checks passed for generated-downloads and configuration-secrets. Pattern proof: 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).

2. November 6, 2026 · canary run  
The same NestJS app deployed with a --release-command migration; the marker it created was readable after activation.

## Tested examples

- **NestJS pattern fixture.** Multi-pattern NestJS app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the GraphQL API itself (your export formats, retention policy and entitlement model) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.