Enforce private-file authorization for Axum · Ample Computer

Enforce private-file authorization for Axum

Private file access for a Axum app on Ample. Verified on Axum: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL.

What it runs on

You need

Exact tested configuration

buildcargo build --release

runtimerust

sizes-1vcpu-2gb

start./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/.d$//')

templateubuntu-24.04

Steps

  1. Build and start. cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL; 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=...
    ```

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 <deployment_id> --kind build
```

How it was checked

✓app responds on its public URL· http get/ → “ample canary axum 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
    Axum pattern fixture deployed on Ample (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL); 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