page:recipes:subscription content:sveltekit:download delivery

Host subscription content with SvelteKit: authorized file delivery

Deploy a subscription content built with SvelteKit 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 SvelteKit: 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 subscription content-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute

    • Status: verified
    • Summary: 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

    • Status: verified
    • Summary: 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

    • Status: verified
    • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Execution Status

Prerequisites

Tested Configuration

Workflow Steps

  1. Build and start
    vite build with @sveltejs/adapter-node then node build on the node-22 template. The server must bind 0.0.0.0 on PORT.

  2. Implement the pattern on PostgreSQL
    The fixture's module implements generated downloads: 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). 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=...

  1. Verify
    Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

    Command: ample logs --kind build

Examples

Success Checks

  1. App responds on its public URL

    • Kind: http_get
    • Path: /
    • Expect: ample canary sveltekit patterns

  2. Generated-downloads self-test

    • Kind: http_get
    • Path: /p/generated-downloads
    • Expect: export=ok rows=3 (with ?token=...; 401 without)

Limitations

Cost Estimate

Evidence Summary

Formats

Next Actions

  1. Action ID: browse-catalog
    • Label: Browse the catalog index
    • Operation ID: catalog_index
    • Method: GET
    • Relative Path: /v1/catalog
    • Requires Authentication: false
  2. Action ID: search-recipes
    • Label: Search published recipes by intent, stack and constraints
    • Operation ID: search_recipes
    • Method: POST
    • Relative Path: /v1/catalog/search
    • Requires Authentication: false
    • Parameters: {"body":{"limit":5,"query":"Host subscription content with SvelteKit: authorized file delivery"}}
  3. Action ID: plan:page:recipes:subscription-content:sveltekit:download-delivery
    • Label: Prepare a side-effect-free deployment plan for an authorized project
    • Operation ID: plan_deployment
    • Method: POST
    • Relative Path: /v1/catalog/plan
    • Requires Authentication: true
    • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:subscription-content:sveltekit:download-delivery","recipeRevision":"r1"}}
  4. Action ID: auth-setup
    • Label: Read the existing agent authentication setup
    • Operation ID: existing_auth_setup
    • Method: GET
    • Relative Path: /mcp/setup
    • Requires Authentication: false
  5. Action ID: browse:workload:subscription-content
    • Label: Browse Subscription content
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Asubscription-content
    • Requires Authentication: false
  6. Action ID: browse:stack:framework-sveltekit
    • Label: Browse SvelteKit
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-sveltekit
    • Requires Authentication: false
  7. Action ID: browse:pattern:generated-downloads
    • Label: Browse Generated downloads
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads
    • Requires Authentication: false
  8. Action ID: browse:intent:deploy-web-app
    • Label: Browse Deploy web app
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app
    • Requires Authentication: false