private file access.md

Enforce private-file authorization for Nuxt

Summary

Private file access for a Nuxt app on Ample. Verified on Nuxt: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template.

Infrastructure requirements

Prerequisites

Exact tested configuration

Steps

  1. Build and start. nuxt build then node .output/server/index.mjs (reads HOST and PORT) 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 <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
  1. 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.
  2. Verify. Fetch the live URL and /api/p/private-document-library on the example; on failure read the build and runtime logs.
   ample logs <deployment_id> --kind build

Tested examples

Success checks

Limitations

Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

Verification evidence

Last verified: 2026-09-20T03:31:44Z

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, databases:read, buckets:read.