### Host approval workflow with ASP.NET Core: downloadable reports

Deploy a approval workflow built with ASP.NET Core 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 ASP.NET Core: 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 approval workflow-specific behavior as your application code.

#### Representative Queries
- Host approval workflow with ASP.NET Core: downloadable reports
- Where can I host Approval workflow built with ASP.NET Core?
- I need an export query, generated artifact retention and authorized download flow.

#### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

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

### Steps to Deploy
1. **Build and start**: `dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to 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). 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.
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) (/p/generated-downloads); then run your own checks.

#### Example
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose generated downloads module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

#### Success Checks
- App responds on its public URL.
- `generated-downloads` self-test.

#### Limitations
- Verified only on the dotnet-10 template at s-1vcpu-1gb. Other sizes, templates and ASP.NET Core major versions are not verified.
- 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.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: Size prices from pricing.toml (loaded by the API).
   - App server: s-1vcpu-1gb
   - Managed PostgreSQL database: s-1vcpu-1gb