page:recipes:client portal:asp net core:private documents

Host client portal with ASP.NET Core: private documents

Deploy a client portal built with ASP.NET Core on Ample using the private document 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. Verified on ASP.NET Core: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the client portal-specific behavior as your application code.

Representative Queries

Host client portal with ASP.NET Core: private documents
Where can I host Client portal built with ASP.NET Core?
I need a role-to-document access model and negative authorization tests.

Prerequisites

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

Workflow Steps

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.
Implement the pattern on PostgreSQL
The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
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.
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=...
Verify
Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) 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
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 client portal itself (your identity integration and role assignments) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

Currency: USD
Monthly Amount: 10.0
Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

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 the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

Canary run: ASP.NET Core pattern fixture deployed on Ample verified, checks passed for private-document-library and configuration-secrets.

Formats

HTML: Link
Markdown: Link
JSON: Link