page:recipes:help desk:asp net core:report exports

Host help desk with ASP.NET Core: downloadable reports

Deploy a help desk 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 help desk-specific behavior as your application code.

Representative Queries

• Host help desk with ASP.NET Core: downloadable reports
• Where can I host Help desk built with ASP.NET Core?
• I need an export query, generated artifact retention and authorized download flow.

Framework

• Framework: ASP.NET Core
• Workload: Help desk
• Release Status: published
• Support Status: verified
• Execution Status: ready

Prerequisites

• A ASP.NET Core project that builds and starts with the documented commands (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT)
• 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

Workflow Steps

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. 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.
   Command: 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.
   Command: ample logs --kind build

Success Checks

• app responds on its public URL
  Kind: http_get
  Path: /
  Expect: ample canary asp net core 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 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 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
• Traits:
  • App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • Managed PostgreSQL database: 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.

Examples

• ASP.NET Core pattern fixture
  Description: Multi-pattern ASP.NET Core app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  Source Ref: tests/deploy-canaries/asp-net-core-patterns.

Evidence Summary

• Canary Run
  Summary: ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); 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-21T01:15:54Z
  Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)
  Expires At: 2027-03-20T01:15:54Z.

Next Actions

• Browse the catalog index
  Action ID: browse-catalog
  Label: Browse the catalog index
  Method: GET
  Parameters: {}

• Search published recipes by intent, stack and constraints
  Action ID: search-recipes
  Label: Search published recipes by intent, stack and constraints
  Method: POST
  Parameters:
  Body: {"limit":5,"query":"Host help desk with ASP.NET Core: downloadable reports"}

• Prepare a side-effect-free deployment plan for an authorized project
  Action ID: plan:page:recipes:help-desk:asp-net-core:report-exports
  Label: Prepare a side-effect-free deployment plan for an authorized project
  Method: POST
  Parameters:
  Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:help-desk:asp-net-core:report-exports","recipeRevision":"r1"}

• Read the existing agent authentication setup
  Action ID: auth-setup
  Label: Read the existing agent authentication setup
  Method: GET
  Parameters: {}

• Browse Help desk
  Action ID: browse:workload:help-desk
  Label: Browse Help desk
  Method: GET
  Parameters: {"nodeId":"workload:help-desk"}

• Browse ASP.NET Core
  Action ID: browse:stack:framework-asp-net-core
  Label: Browse ASP.NET Core
  Method: GET
  Parameters: {"nodeId":"stack:framework-asp-net-core"}

• Browse Generated downloads
  Action ID: browse:pattern:generated-downloads
  Label: Browse Generated downloads
  Method: GET
  Parameters: {"nodeId":"pattern:generated-downloads"}

• Browse Deploy web app
  Action ID: browse:intent:deploy-web-app
  Label: Browse Deploy web app
  Method: GET
  Parameters: {"nodeId":"intent:deploy-web-app"}