Host reporting dashboard with ASP.NET Core: file attachments · Ample Computer
Host reporting dashboard with ASP.NET Core: file attachments
Deploy a reporting dashboard built with ASP.NET Core on Ample using the browser file uploads 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: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). The reporting dashboard-specific behavior (your upload UI, allowed types, size limits and virus scanning) is your application code on that verified basis.
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
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 createwith its credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, databases:read, buckets:read
Exact tested configuration
build dotnet publish -c Release -o out
runtime dotnet
sizes-1vcpu-1gb
start ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll
template dotnet-10
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 browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=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 needs an answer first). 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=...
- Verify. Fetch the live URL and the pattern self-test route(s) (/p/browser-file-uploads) from the example; then run your own checks. On failure read
ample logs <deployment_id> --kind buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary asp net core patterns”
✓ browser-file-uploads self-test· http get/p/browser-file-uploads → “reject=ok upload=ok linked=ok”
Evidence
- November 6, 2026 · canary run
ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet
- November 5, 2026 · canary run
The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.
Tested examples
- ASP.NET Core pattern fixture. Multi-pattern ASP.NET Core app whose browser file uploads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture.
The pattern checks verified the platform side; the reporting dashboard itself (your upload UI, allowed types, size limits and virus scanning) is your application code.
Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.