### Host partner portal with ASP.NET Core: private documents

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

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

#### Resource Requirements  
- `primitive:compute`  
- `primitive:postgres`  
- `primitive:s3-compatible-object-storage`

#### 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.

#### 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  
1. **Build and start**:  
   Run `dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.
2. **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).
3. **Wire object storage**:  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
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) (/p/private-document-library) from the example; then run your own checks.

#### Examples  
- **ASP.NET Core pattern fixture**:  
   Multi-pattern ASP.NET Core app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

#### Success Checks  
1. App responds on its public URL
2. Private-document-library self-test

#### 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 partner portal itself (your identity integration and role assignments) is application code and was not separately tested.

#### Cost Estimate  
- **Monthly Amount**:  $10.00 USD  
   - Components:  
   - App server:  s-1vcpu-1gb (1.0 instance) - $5.00/month  
   - Managed PostgreSQL database (1.0 instance) - $5.00/month  
   - 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.