# Connect Postgres for ASP.NET Core

## Summary

Database connection for an ASP.NET Core app on Ample. Verified on ASP.NET Core: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok). Build and start: `dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.

## Infrastructure requirements

- **Compute**: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
- **Postgres**: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)

## Prerequisites

- A ASP.NET Core project (`dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT)
- A PostgreSQL driver reading DATABASE_URL at runtime
- An Ample account token with `servers:write`, `databases:read`

## Exact tested configuration

- template: `dotnet-10`
- runtime: `dotnet`
- size: `s-1vcpu-1gb`
- build: `dotnet publish -c Release -o out`
- start: `ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll`

## Steps

1. **Build and start.** `dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT; the server must bind `0.0.0.0` on PORT.
2. **Read DATABASE_URL at runtime.** Open connections from the environment inside handlers or a pool; omit DATABASE_URL to auto-provision a managed database or pass `--env DATABASE_URL=...` for an existing one.
3. **Verify.** Fetch the live URL and `/p/relational-records` on the example; on failure read the build and runtime logs.
   
   ```
   ample logs <deployment_id> --kind build
   ```

## Tested examples

- **ASP.NET Core pattern fixture** (tests/deploy-canaries/asp-net-core-patterns): Verified database connection on ASP.NET Core.

## Success checks

- App responds on its public URL (`/` on the live URL, expect ample canary asp net core patterns)
- Relational-records check from the example (`/p/relational-records` on the live URL, expect to see the pattern fixture checks)

## Limitations

- Verified on the dotnet-10 template at `s-1vcpu-1gb`; other sizes and ASP.NET Core major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

## Cost estimate

Estimated **10.00 USD** per month (size prices from `pricing.toml` at build revision `a1b8c38919e59cd035ebabaced73cf84ece24371`).
- app server x1 `s-1vcpu-1gb`: **5.00 USD**
- managed PostgreSQL database x1 `s-1vcpu-1gb`: **5.00 USD**

Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-21T01:15:54Z at revision `50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)`: ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); for this guide: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok). (expires 2027-03-20T01:15:54Z)

Last verified: 2026-09-21T01:15:54Z

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-21T03:19:59.461917+00:00 at revision `49962bcade4f`, binding state `current`, required scopes: `servers:write`, `databases:read`.