Enforce private-file authorization for ASP.NET Core · Ample Computer
Enforce private-file authorization for ASP.NET Core
Private file access for a ASP.NET Core app on Ample. Verified on ASP.NET Core: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.
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_URLis 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 (
dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT) - A PostgreSQL driver reading
DATABASE_URLat runtime - A bucket from
ample bucket createwith credentials passed as encryptedS3_*environment variables - An 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 outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT; the server must bind0.0.0.0onPORT.Create the bucket and pass its credentials. Create it once with
ample bucket create, then pass endpoint, region, bucket and keys with--env; use path-style addressing.
$ 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=...
Authorize before touching storage. Return 401 for unauthenticated requests and 403 for the wrong role; keep the bucket unpublished and stream objects through the app.
Verify. Fetch the live URL and
/p/private-document-libraryon the example; on failure read the build and runtime logs.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL · http get/ → “ample canary asp net core patterns”
✓ private-document-library check from the example · http get/p/private-document-library → “see the pattern fixture checks”
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 <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); for this guide: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok).
Tested examples
- ASP.NET Core pattern fixture. Verified private file access on ASP.NET Core.
What it doesn’t cover
- Verified on the dotnet-10 template at
s-1vcpu-1gb. - Managed PostgreSQL 16 with pgvector.
- 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.