page:recipes:subscription content:asp net core:download delivery

Host subscription content with ASP.NET Core: authorized file delivery

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

Representative Queries

Resource Requirements

Infrastructure Requirements

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

Framework

Workload

Release Status

Support Status

Execution Status

Prerequisites

  1. 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).
  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. 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.
  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.

Examples

ASP.NET Core pattern fixture

Success Checks

Limitations

Cost Estimate

Evidence Summary

  1. Kind: Canary Run
    Summary: ASP.NET Core pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
    Observed At: 2026-09-21T01:15:54Z
    Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)
    Expires At: 2027-03-20T01:15:54Z
    Scope:
    • Checks: /p/generated-downloads
    • Pattern: pattern:generated-downloads
    • Template: dotnet-10
  2. Kind: Canary Run
    Summary: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.
    Observed At: 2026-09-20T23:34:47Z
    Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
    Expires At: 2027-03-19T23:34:47Z
    Scope:
    • Pattern: pattern:generated-downloads

Next Actions

  1. Browse the catalog index

    • Action ID: browse-catalog
    • Method: GET
    • Relative Path: /v1/catalog

  2. Search published recipes by intent, stack and constraints

    • Action ID: search-recipes
    • Method: POST
    • Relative Path: /v1/catalog/search
    • Parameters:
      • Body:
        • Limit: 5
        • Query: Host subscription content with ASP.NET Core: authorized file delivery

  3. Prepare a side-effect-free deployment plan for an authorized project

    • Action ID: plan:page:recipes:subscription-content:asp-net-core:download-delivery
    • Method: POST
    • Relative Path: /v1/catalog/plan
    • Parameters:
      • Body:
        • Inputs: {}
        • Project ID: ""
        • Recipe ID: page:recipes:subscription-content:asp-net-core:download-delivery
        • Recipe Revision: r1

  4. Read the existing agent authentication setup

    • Action ID: auth-setup
    • Method: GET
    • Relative Path: /mcp/setup

  5. Browse Subscription content

    • Action ID: browse:workload:subscription-content
    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Asubscription-content

  6. Browse ASP.NET Core

    • Action ID: browse:stack:framework-asp-net-core
    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-asp-net-core

  7. Browse Generated downloads

    • Action ID: browse:pattern:generated-downloads
    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads

  8. Browse Deploy web app

    • Action ID: browse:intent:deploy-web-app
    • Method: GET
    • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app