Host Admin Dashboard with ASP.NET Core: Public Profile Assets

Deploy an admin dashboard built with ASP.NET Core on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the admin dashboard-specific behavior as your application code.

Representative Queries

• Host admin dashboard with ASP.NET Core: public profile assets
• Where can I host Admin dashboard built with ASP.NET Core?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

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

Framework

ASP.NET Core

Workload

Admin dashboard

Release Status

Published

Execution Status

Ready

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
   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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization. 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. Publish only the bucket that serves public assets and reference its CDN URL.
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 --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
   Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   ample logs --kind build

Success Checks

• App responds on its public URL
  Kind: http_get
  Path: /
  Expect: ample canary asp net core patterns
• Public-media-library self-test Kind: http_get
  Path: /p/public-media-library
  Expect: a CDN URL whose content is served publicly
• Private-document-library self-test
  Kind: http_get
  Path: /p/private-document-library
  Expect: private=ok (with ?role=owner; 401 without, 403 for viewer)

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 admin dashboard itself was not separately tested; the pattern checks are what was verified.
• 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 and backup procedures are not verified.
• The CDN serves published-bucket objects only; cache rules are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
• Note: Always-on monthly price of tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Summary of ASP.NET Core pattern fixture deployed on Ample; checks passed for public-media-library and private-document-library.

Last Verified At

2026-09-21T01:15:54Z