Host form collection with ASP.NET Core: data exports

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

Representative Queries

• Host form collection with ASP.NET Core: data exports
• Where can I host Form collection built with ASP.NET Core?
• I need a scoped export format, artifact generation and authorized download procedure.

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.

Prerequisites

1. A ASP.NET Core project that builds and starts with 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
4. 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.
2. Implement the pattern on PostgreSQL: The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored in a private bucket and returned only to an authorized caller.
3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and run your own checks.

Limitations

• Verified on the dotnet-10 template at s-1vcpu-1gb; other sizes, templates and ASP.NET Core major versions are not verified.
• The form collection (your export formats, retention policy and entitlement model) is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • app server: s-1vcpu-1gb (1.0): $5.00
  • managed PostgreSQL database: s-1vcpu-1gb (1.0): $5.00

Evidence Summary

• Canary Run: ASP.NET Core pattern fixture deployed on Ample; checks passed for generated-downloads. Pattern proof: an export query rendered to a CSV artifact stored in a private bucket returned only to an authorized caller.

Next Actions

• Browse the catalog index: /v1/catalog
• Search published recipes by intent: /v1/catalog/search
• Prepare a side-effect-free deployment plan: /v1/catalog/plan
• Read the existing agent authentication setup: /mcp/setup
• Browse Form collection: /v1/catalog/nodes/workload%3Aform-collection
• Browse ASP.NET Core: /v1/catalog/nodes/stack%3Aframework-asp-net-core