Enforce private-file authorization for Phoenix · Ample Computer

Enforce private-file authorization for Phoenix

Private file access for a Phoenix app on Ample. Verified on Phoenix: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

build MIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite
install mix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod
runtime elixir
sizes -1vcpu-1gb start PHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start

Steps

  1. Build and start. mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs; 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 phoenix 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
    Phoenix pattern fixture deployed on Ample (mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs); 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