### Host inventory manager with ASP.NET Core: private attachments

Deploy an inventory manager 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 inventory manager-specific behavior as your application code.

#### Representative Queries
- Host inventory manager with ASP.NET Core: private attachments
- Where can I host Inventory manager built with ASP.NET Core?
- I need attachment metadata, access checks, and a tested private object access path.

#### 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
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- **S3-compatible object storage**: 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 private document library with necessary tests and checks.
3. **Wire object storage**: Create the bucket(s), then pass endpoint, region, bucket, and keys as --env values; use path-style addressing.
4. **Deploy**: Execute the synchronous deploy command and check the exit status.
5. **Verify**: Check the live URL and pattern self-test routes, and review logs if any failures occur.

#### Examples
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose private document library module was checked live.

#### Success Checks
- **App responds on its public URL**: Validate with an HTTP GET request.
- **Private-document-library self-test**: Validate access control with an HTTP GET request.

#### Limitations
- Only verified on the dotnet-10 template. Other sizes and configurations are not tested.
- The inventory manager behavior is application-specific and not verified separately.

#### Cost Estimate
- **Monthly Amount**: $10.00 (USD)
- **Components**:
  - App Server: $5.00
  - Managed PostgreSQL Database: $5.00

#### Last Verified At
- 2026-09-21T01:15:54Z

#### Next Actions
- Browse the catalog index
- Search published recipes by intent, stack, and constraints
- Prepare a deployment plan for an authorized project
- Read the existing authentication setup
- Browse Inventory manager
- Browse ASP.NET Core
- Browse Private document library
- Browse Deploy web app