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

Host vendor portal with ASP.NET Core: private documents

Summary

Deploy a vendor 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 vendor portal-specific behavior as your application code.

Representative Queries

• Host vendor portal with ASP.NET Core: private documents
• Where can I host Vendor 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

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.

Tested Configuration

• Template: dotnet-10
• Runtime: dotnet
• Size: s-1vcpu-1gb
• Build Command: dotnet publish -c Release -o out
• Start Command: ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll

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 a role-to-document access model with negative tests and a private-bucket round-trip for the allowed role. 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.
4. Deploy
   • Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. Verify
   • Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks. On failure read logs.

Success Checks

1. App responds on its public URL: ample canary asp net core patterns
2. Private-document-library self-test: 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.
• The vendor portal itself (identity integration and role assignments) is application code and was not separately tested.

Cost Estimate

• Monthly Amount: $10.00
• Basis: size prices from pricing.toml (loaded by the API)
• Components:
  • App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

1. Browse the catalog index: GET /v1/catalog
2. Search published recipes: POST /v1/catalog/search
3. Prepare deployment plan: POST /v1/catalog/plan
4. Read existing authentication setup: GET /mcp/setup
5. Browse Vendor portal: GET /v1/catalog/nodes/workload%3Avendor-portal
6. Browse ASP.NET Core: GET /v1/catalog/nodes/stack%3Aframework-asp-net-core
7. Browse Private document library: GET /v1/catalog/nodes/pattern%3Aprivate-document-library
8. Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app