Enforce private-file authorization for SvelteKit

Summary

Private file access for a SvelteKit app on Ample. Verified on SvelteKit: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: vite build with @sveltejs/adapter-node then node build on the node-22 template.

Prerequisites

• A SvelteKit project (vite build with @sveltejs/adapter-node then node build on the node-22 template)
• A PostgreSQL driver reading DATABASE_URL at runtime
• A bucket from ample bucket create with credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, databases:read, buckets:read

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

Workload

Enforce private-file authorization

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

   ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   

3. Authorize before touching storage: Return 401 for unauthenticated requests and 403 for the wrong role; keep the bucket unpublished and stream objects through the app.
4. Verify: Fetch the live URL and /p/private-document-library on the example; on failure read the build and runtime logs.

   ample logs  --kind build
   

Examples

• SvelteKit pattern fixture: Verified private file access on SvelteKit.

Success Checks

• App responds on its public URL.
  • Check: ample canary sveltekit patterns
• Private-document-library check from the example.
  • Check: See the pattern fixture checks.

Limitations

• Verified on the node-22 template at s-1vcpu-1gb; other sizes and SvelteKit major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App server: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.00
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.00

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan

Formats

• HTML format
• Markdown format
• JSON format