page:recipes:order tracking:asp net core:download delivery

Host order tracking with ASP.NET Core: authorized file delivery

Deploy a order tracking built with ASP.NET Core on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the order tracking-specific behavior as your application code.

Representative Queries

• Host order tracking with ASP.NET Core: authorized file delivery
• Where can I host Order tracking built with ASP.NET Core?
• I need a file entitlement model and an application-enforced download authorization flow.

Parent Resources

• Order tracking: Canonical Path
• ASP.NET Core: Canonical Path
• Generated downloads: Canonical Path
• Deploy web app: Canonical Path

Resource Requirements

• Compute
• PostgreSQL
• S3-compatible object storage

Infrastructure Requirements

1. Compute: 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: 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: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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: 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. Keep private data in an unpublished bucket.
4. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
5. Verify: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

Examples

• ASP.NET Core pattern fixture: Multi-pattern ASP.NET Core app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL: ample canary asp net core patterns.
• Generated-downloads self-test: export=ok rows=3 (with ?token=...; 401 without).

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 order tracking itself (your export formats, retention policy and entitlement model) is application code and was not separately tested.

Cost Estimate

• Monthly Amount: $10.00
  • App Server: $5.00 (Size: s-1vcpu-1gb, Quantity: 1.0)
  • Managed PostgreSQL Database: $5.00 (Size: s-1vcpu-1gb, Quantity: 1.0)

Evidence Summary

1. Canary run: ASP.NET Core pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
2. Canary run: The same ASP.NET Core app deployed with a --release-command migration.

Unknowns

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

Formats

• HTML
• Markdown
• JSON

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Order tracking
6. Browse ASP.NET Core
7. Browse Generated downloads
8. Browse Deploy web app