Enforce private-file authorization for React Router · Ample Computer

Enforce private-file authorization for React Router

Private file access for a React Router app on Ample. Verified on React Router: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: react-router build then react-router-serve on the node-22 template.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build npm run build --if-present

install npm install

runtime node

sizes-1vcpu-1gb

start npm run start

template node-22

Steps

  1. Build and start. react-router build then react-router-serve 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 react router patterns”
✓ private-document-library check from the example· http get/p/private-document-library → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run

React Router pattern fixture deployed on Ample (react-router build then react-router-serve 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