# Host graphql api with Echo: stored input and output artifacts

Deploy a graphql api built with Echo 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 Echo: 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 Echo: stored input and output artifacts
- Where can I host GraphQL API built with Echo?
- I need an input/output artifact contract, object metadata and access boundaries.

## 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 Echo project that builds and starts with the documented commands (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
- 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

## Tested Configuration
- Template: ubuntu-24.04  
- Runtime: go  
- Size: s-1vcpu-1gb  
- Build: CGO_ENABLED=0 go build -o app ./...  
- Start: ./app

## Workflow Steps
1. **Build and start**  
   CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build). 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.
   ```bash
   ample deploy . --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  --kind build` then `--kind runtime`.
   ```bash
   ample logs  --kind build
   ```

## Success Checks
- **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary echo patterns
- **Generated-downloads self-test**  
   - Kind: http_get  
   - Path: /p/generated-downloads  
   - Expect: export=ok rows=3 (with ?token=...; 401 without)

## Limitations
- Verified on the ubuntu-24.04 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Echo 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.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

## Cost Estimate
- Currency: USD  
- Monthly Amount: 10.0  
- Authoritative: true  
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- Components:  
  - **App server**  
    - Size: s-1vcpu-1gb  
    - Quantity: 1.0  
    - Monthly Amount: 5.0  
  - **Managed PostgreSQL database**  
    - Size: s-1vcpu-1gb  
    - Quantity: 1.0  
    - Monthly Amount: 5.0  
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Canary Run**: Echo pattern fixture deployed on Ample (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build)); 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). Observed at: 2026-09-21T02:34:39Z.
- **Canary Run**: The same Echo app deployed with a --release-command migration; the marker it created was readable after activation. Observed at: 2026-09-20T02:43:30Z.

## Next Actions
- **Browse the catalog index**  
   - Action ID: browse-catalog  
   - Method: GET  
   - Relative Path: /v1/catalog  
- **Search published recipes by intent, stack and constraints**  
   - Action ID: search-recipes  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
   - Parameters:  
     - Body: {"limit":5,"query":"Host graphql api with Echo: stored input and output artifacts"}
- **Prepare a side-effect-free deployment plan for an authorized project**  
   - Action ID: plan:page:recipes:graphql-api:echo:artifact-storage  
   - Method: POST  
   - Relative Path: /v1/catalog/plan  
   - Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:graphql-api:echo:artifact-storage","recipeRevision":"r1"}}
- **Read the existing agent authentication setup**  
   - Action ID: auth-setup  
   - Method: GET  
   - Relative Path: /mcp/setup  
- **Browse GraphQL API**  
   - Action ID: browse:workload:graphql-api  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/workload%3Agraphql-api  
- **Browse Echo**  
   - Action ID: browse:stack:framework-echo  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-echo  
- **Browse Generated downloads**  
   - Action ID: browse:pattern:generated-downloads  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads  
- **Browse Deploy API**  
   - Action ID: browse:intent:deploy-api  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-api