Host digital downloads with ASP.NET Core: public product media

Summary

Deploy a digital downloads built with ASP.NET Core on Ample using the public media 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, and a published bucket serves public assets from the CDN host. Verified on ASP.NET Core: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.

Main Article Content

Representative Queries

• Host digital downloads with ASP.NET Core: public product media
• Where can I host Digital downloads built with ASP.NET Core?
• I need product-to-object mappings and a tested public media delivery path.

Resource Requirements

• Compute
• Postgres
• S3-compatible object storage
• CDN

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.

4. CDN

   • Status: Verified
   • Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

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 .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 and a second, published bucket for public assets (CDN_*)
• An Ample account token with servers:write, databases:read, buckets:read

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.

2. Implement the pattern on PostgreSQL

   • Summary: The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.

3. Wire object storage

   • Summary: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing.

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=... --env CDN_PUBLIC_URL=...

5. Verify

   • Command: ample logs --kind build then --kind runtime.

Examples

• ASP.NET Core pattern fixture: Multi-pattern ASP.NET Core app whose public media library module was checked live.

Success Checks

1. App responds on its public URL

   • Expect: ample canary asp net core patterns

2. Public-media-library self-test

   • Expect: a CDN URL whose content is served publicly

Limitations

• Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb (Monthly Amount: 5.0)
  • Managed PostgreSQL database: s-1vcpu-1gb (Monthly Amount: 5.0)

Evidence Summary

• Canary Run: ASP.NET Core pattern fixture deployed on Ample (checks passed for public-media-library and configuration-secrets).

Next Actions

1. Browse the catalog index

   • Operation ID: catalog_index

2. Search published recipes

   • Operation ID: search_recipes

3. Prepare a side-effect-free deployment plan

   • Operation ID: plan_deployment

4. Read the existing agent authentication setup

   • Operation ID: existing_auth_setup

5. Browse Digital downloads

   • Operation ID: browse_node