### Host approval workflow with ASP.NET Core: private attachments

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

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

#### Resource Requirements
- Compute
- PostgreSQL
- S3-compatible object storage

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

#### Prerequisites
1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
4. An Ample account token with servers:write, databases:read, buckets:read.

#### Tested Configuration
- **Template**: dotnet-10
- **Runtime**: dotnet
- **Size**: s-1vcpu-1gb
- **Build**: dotnet publish -c Release -o out
- **Start**: 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 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). 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). Re-running with no change is a no-op. Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`.
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. On failure read `ample logs --kind build` then `--kind runtime`. Command: `ample logs --kind build`.

#### Success Checks
- Application responds on its public URL: **Expect** `ample canary asp net core patterns`.  
- Private-document-library self-test: **Expect** `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; other sizes, templates and ASP.NET Core major versions are not verified.
- The approval workflow itself (your identity integration and role assignments) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.

**Components**:
- App server: s-1vcpu-1gb - 5.0
- Managed PostgreSQL database: s-1vcpu-1gb - 5.0

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

#### Evidence Summary
1. **Canary Run**: ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); checks passed for private-document-library and configuration-secrets.
   - **Observed At**: 2026-09-21T01:15:54Z
2. **Canary Run**: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.
   - **Observed At**: 2026-09-20T23:34:47Z

#### Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

#### Formats
- [HTML version](/content/recipes/approval-workflow/asp-net-core/private-attachments/index.html)
- [Markdown version](/content/recipes/approval-workflow/asp-net-core/private-attachments.md)
- [JSON version](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aapproval-workflow%3Aasp-net-core%3Aprivate-attachments)

#### Next Actions
- [Browse the catalog index](https://api.ample.com/v1/catalog)
- [Search published recipes by intent, stack and constraints](https://api.ample.com/v1/catalog/search)
- [Prepare a side-effect-free deployment plan for an authorized project](https://api.ample.com/v1/catalog/plan)
- [Read the existing agent authentication setup](https://api.ample.com/mcp/setup)
- [Browse Approval workflow](https://api.ample.com/v1/catalog/nodes/workload%3Aapproval-workflow)
- [Browse ASP.NET Core](https://api.ample.com/v1/catalog/nodes/stack%3Aframework-asp-net-core)
- [Browse Private document library](https://api.ample.com/v1/catalog/nodes/pattern%3Aprivate-document-library)
- [Browse Deploy web app](https://api.ample.com/v1/catalog/nodes/intent%3Adeploy-web-app)