Enforce private-file authorization for Hono · Ample Computer

Enforce private-file authorization for Hono

Private file access for a Hono app on Ample. Verified on Hono: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: npm install and npm run start with @hono/node-server on the node-22 template.

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. npm install and npm run start with @hono/node-server 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 /p/private-document-library on the example; on failure read the build and runtime logs.

   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary hono patterns”
✓ private-document-library check from the example · http get/p/private-document-library → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run

Hono pattern fixture deployed on Ample (npm install and npm run start with @hono/node-server on the node-22 template); for this guide: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok).

Tested examples

What it doesn’t cover