# Configure S3-compatible access for ASP.NET Core

## Summary
Object storage client for a ASP.NET Core app on Ample. Verified on ASP.NET Core: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=ok). 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.

## Representative Queries
- Configure S3-compatible access for ASP.NET Core
- Where can I host Configure S3-compatible access built with ASP.NET Core?
- I need exact S3 endpoint, credentials, operation requirements and an upload/download verification.

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

## 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. **Create the bucket and pass its credentials**  
   Create it once with `ample bucket create`, then pass endpoint, region, bucket and keys with --env; use path-style addressing.  
   Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`
3. **Verify**  
   Fetch the live URL and `/p/browser-file-uploads` on the example; on failure read the build and runtime logs.  
   Command: `ample logs --kind build`

## Examples
- **ASP.NET Core pattern fixture**: Verified object storage client on ASP.NET Core.

## Success Checks
- App responds on its public URL (kind: `http_get`, path: `/`, expect: `ample canary asp net core patterns`)
- Browser-file-uploads check from the example (kind: `http_get`, path: `/p/browser-file-uploads`, expect: `see the pattern fixture checks`)

## Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb; other sizes and ASP.NET Core major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- PutObject and GetObject with path-style addressing are verified; other S3 operations are not.

## Cost Estimate
- Currency: USD
- Monthly Amount: 5.0
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- Components:
  - Name: app server
    Size: s-1vcpu-1gb
    Quantity: 1.0
    Monthly Amount: 5.0
- Note: Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- Kind: canary_run
- Summary: 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);  for this guide: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=ok).
- Observed At: 2026-09-21T01:15:54Z
- Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)
- Expires At: 2027-03-20T01:15:54Z

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

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