Host graphql api with FastAPI: stored input and output artifacts

Deploy a graphql api built with FastAPI 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 FastAPI: 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

• Host graphql api with FastAPI: stored input and output artifacts
• Where can I host GraphQL API built with FastAPI?
• I need an input/output artifact contract, object metadata and access boundaries.

Parent IDs

• GraphQL API
• FastAPI
• Generated downloads
• Deploy API

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

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.

Prerequisites

• A FastAPI project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 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
• An Ample account token with servers:write, databases:read, buckets:read

Workflow Steps

1. Build and start: pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 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). Re-running with no change is a no-op.
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 --kind build then --kind runtime.

Success Checks

1. app responds on its public URL
2. generated-downloads self-test

Limitations

• Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and FastAPI major versions are not verified.
• The graphql api itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Next Actions

1. Browse the catalog index: GET /v1/catalog
2. Search published recipes: POST /v1/catalog/search
3. Prepare a deployment plan: POST /v1/catalog/plan
4. Read existing agent authentication setup: GET /mcp/setup
5. Browse GraphQL API: GET /v1/catalog/nodes/workload%3Agraphql-api
6. Browse FastAPI: GET /v1/catalog/nodes/stack%3Aframework-fastapi
7. Browse Generated downloads: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
8. Browse Deploy API: GET /v1/catalog/nodes/intent%3Adeploy-api