---
title: "Host event registration with ASP.NET Core: data exports"
description: "Deploy a event registration built with ASP.NET Core on Ample using the generated downloads pattern."
canonical_url: "https://ample.computer/recipes/event-registration/asp-net-core/data-exports"
last_updated: "2026-09-21"
---

# Host event registration with ASP.NET Core: data exports

Canonical URL: https://ample.computer/recipes/event-registration/asp-net-core/data-exports
Formats: [HTML](https://ample.computer/recipes/event-registration/asp-net-core/data-exports) | [Markdown](https://ample.computer/recipes/event-registration/asp-net-core/data-exports.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aevent-registration%3Aasp-net-core%3Adata-exports)
Recipe ID: `page:recipes:event-registration:asp-net-core:data-exports` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e`

Status: release `published`, support `verified`, execution `ready`

## Summary

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

Path: [Agent hosting discovery](/discover/discovery) / [Applications and workloads](/discover/workload) / [Scheduling and data](/discover/workload/scheduling-and-data) / [Event registration](/discover/workload/event-registration) / [Host event registration with ASP.NET Core: data exports](/recipes/event-registration/asp-net-core/data-exports)

## Infrastructure requirements

- [Compute](/discover/primitive/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](/discover/primitive/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.)
- [S3-compatible object storage](/discover/primitive/s3-compatible-object-storage): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## Prerequisites

- An ASP.NET Core project that builds and starts with the documented commands (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 (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

## 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. **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.

   ```
   ample deploy . --name <app-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 <deployment_id> --kind build` then `--kind runtime`.

   ```
   ample logs <deployment_id> --kind build
   ```

## Tested examples

- **ASP.NET Core pattern fixture** (tests/deploy-canaries/asp-net-core-patterns): 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 (`/` on the live URL, expect ample canary asp net core patterns)
- generated-downloads self-test (`/p/generated-downloads` on the live URL, expect export=ok rows=3 (with ?token=...; 401 without))


## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7).
- 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 and databases 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 (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); 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). (expires 2027-03-20T01:15:54Z)
- canary_run on 2026-09-20T23:34:47Z at revision `4d1511e574302f3904b75088bd4048a0975218b3 (CLI 0.1.21)`: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation. (expires 2027-03-19T23:34:47Z)

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


## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`, binding state `current`, required scopes: servers:write, databases:read, buckets:read.

## Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "env": {
      "description": "Encrypted environment variables (bucket credentials, secrets)",
      "items": {
        "pattern": "^[A-Z][A-Z0-9_]*=.*$",
        "type": "string"
      },
      "maxItems": 50,
      "type": "array"
    },
    "name": {
      "description": "App name",
      "maxLength": 63,
      "minLength": 1,
      "pattern": "^[a-z0-9-]+$",
      "type": "string"
    },
    "path": {
      "description": "Project directory or ample.toml service",
      "maxLength": 512,
      "minLength": 1,
      "type": "string"
    },
    "release_command": {
      "description": "Migration command run before activation",
      "maxLength": 512,
      "type": "string"
    }
  },
  "required": [
    "env",
    "name",
    "path"
  ],
  "type": "object"
}
```

## Next actions

- Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false)
- Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false)
- Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false)
- Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false)
- Browse Event registration (GET /v1/catalog/nodes/workload%3Aevent-registration on the api origin; auth: false, approval: false)
- Browse ASP.NET Core (GET /v1/catalog/nodes/stack%3Aframework-asp-net-core on the api origin; auth: false, approval: false)
- Browse Generated downloads (GET /v1/catalog/nodes/pattern%3Agenerated-downloads on the api origin; auth: false, approval: false)
- Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; auth: false, approval: false)

Actions describe possible next steps. They are typed data, not commands, and grant no permission.