page:recipes:graphql api:fastify:artifact storage

Host graphql api with Fastify: stored input and output artifacts

Deploy a graphql api built with Fastify 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 Fastify: 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 graphql api-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
  2. 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.
  3. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Framework

Fastify

Workload

GraphQL API

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

Input Schema

{
  "additionalProperties": false,
  "properties": {
    "env": {
      "description": "Encrypted environment variables (bucket credentials, secrets)",
      "items": {"pattern":"^[A-Z][A-Z0-9_]*=.*$","type":"string"},
      "maxItems": 50,
      "type": "array"
    },
    "name": {
      "description": "App name",
      "maxLength": 63,
      "minLength": 1,
      "pattern": "^[a-z0-9-]+$",
      "type": "string"
    },
    "path": {
      "description": "Project directory or ample.toml service",
      "maxLength": 512,
      "minLength": 1,
      "type": "string"
    },
    "release_command": {
      "description": "Migration command run before activation",
      "maxLength": 512,
      "type": "string"
    }
  },
  "required": ["env", "name", "path"],
  "type": "object"
}

Workflow Steps

  1. Build and start: npm install, npm run build --if-present, npm run start on the node-22 template. The server must bind 0.0.0.0 on PORT.
  2. Implement the pattern on PostgreSQL: 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.
  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) and then run your own checks.

Examples

Success Checks

  1. App responds on its public URL: ample canary fastify patterns
  2. Generated-downloads self-test: export=ok rows=3 (with ?token=...; 401 without)

Limitations

Cost Estimate

Evidence Summary

Next Actions