Host partner portal with ASP.NET Core: public profile assets

Deploy a partner portal built with ASP.NET Core on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host. Verified on ASP.NET Core: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the partner portal-specific behavior as your application code.

Representative Queries

• Host partner portal with ASP.NET Core: public profile assets
• Where can I host Partner portal built with ASP.NET Core?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

• compute
• postgres
• s3-compatible-object-storage
• cdn

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 verified by canary. Other S3 operations are not verified.

CDN

• The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role).

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

5. Verify
   Fetch the live URL and the pattern self-test routes from the example; then run your checks.

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 partner portal itself (your image processing and profile-media rules) is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: Size prices from pricing.toml at build revision ...

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.

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