# Host Help Desk with ASP.NET Core: Private Attachments

## Summary
Deploy a help desk built with ASP.NET Core on Ample using the private document library 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.

## Representative Queries
- Host help desk with ASP.NET Core: private attachments
- Where can I host Help desk built with ASP.NET Core?
- I need attachment metadata, access checks, and a tested private object access path.

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

## Infrastructure Requirements
1. **Compute**  
   Status: verified  
   Summary: 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**  
   Status: verified  
   Summary: 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**  
   Status: verified  
   Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Workflow Steps
1. **Build and start**  
   Command: `dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). 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**  
   Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`  
   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/private-document-library) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.

## Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates, and ASP.NET Core major versions are not verified.
- The help desk itself (your identity integration and role assignments) 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.

## Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** $10.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.

### Components
1. **App server**  
   Size: `s-1vcpu-1gb`  
   Quantity: 1.0  
   Monthly Amount: $5.0
2. **Managed PostgreSQL database**  
   Size: `s-1vcpu-1gb`  
   Quantity: 1.0  
   Monthly Amount: $5.0

## Examples
- **Title:** ASP.NET Core pattern fixture  
  **Description:** Multi-pattern ASP.NET Core app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  **Source Ref:** tests/deploy-canaries/asp-net-core-patterns

## Next Actions
1. **Action:** Browse the catalog index  
   Method: GET  
   Relative Path: /v1/catalog
2. **Action:** Search published recipes by intent, stack and constraints  
   Method: POST  
   Relative Path: /v1/catalog/search
3. **Action:** Prepare a side-effect-free deployment plan for an authorized project  
   Method: POST  
   Relative Path: /v1/catalog/plan
4. **Action:** Read the existing agent authentication setup  
   Method: GET  
   Relative Path: /mcp/setup
5. **Action:** Browse Help desk  
   Method: GET  
   Relative Path: /v1/catalog/nodes/workload%3Ahelp-desk
6. **Action:** Browse ASP.NET Core  
   Method: GET  
   Relative Path: /v1/catalog/nodes/stack%3Aframework-asp-net-core  
7. **Action:** Browse Private document library  
   Method: GET  
   Relative Path: /v1/catalog/nodes/pattern%3Aprivate-document-library  
8. **Action:** Browse Deploy web app  
   Method: GET  
   Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app