Host reporting dashboard with FastAPI: data exports · Ample Computer

Host reporting dashboard with FastAPI: data exports

Deploy a reporting dashboard 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). The reporting dashboard-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

install

python3 -m pip install --target .ample/python -r requirements.txt

runtime

python

sizes

1vcpu-1gb

start

PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

template

python-3.12

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

   $ ample deploy . --name <app-name> --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
  1. 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.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL· http get/ → “ample canary fastapi 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
    FastAPI pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 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 FastAPI app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover