# Host reporting dashboard with ASP.NET Core: file attachments

Deploy a reporting dashboard built with ASP.NET Core on Ample using the browser file uploads 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: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). Not separately tested: your upload UI, allowed types, size limits and virus scanning; treat the reporting dashboard-specific behavior as your application code.

## Representative Queries
- Host reporting dashboard with ASP.NET Core: file attachments
- Where can I host Reporting dashboard built with ASP.NET Core?
- I need a restricted upload flow, file validation and record-to-object linkage.

## 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**: 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 browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=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/browser-file-uploads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`. Command: `ample logs  --kind build`

## 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 reporting dashboard itself (your upload UI, allowed types, size limits and virus scanning) 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.

## Success Checks
1. App responds on its public URL  
   **Kind**: http_get  
   **Path**: /  
   **Expect**: ample canary asp net core patterns
2. Browser-file-uploads self-test  
   **Kind**: http_get  
   **Path**: /p/browser-file-uploads  
   **Expect**: reject=ok upload=ok linked=ok

## Costs
- **Monthly Estimate**: 10.0 USD  
   **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
   **Components**:
    - App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0  
    - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 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.
 
## Example
- **Title**: ASP.NET Core pattern fixture  
  **Description**: Multi-pattern ASP.NET Core app whose browser file uploads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  **Source Reference**: tests/deploy-canaries/asp-net-core-patterns.