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
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
An Axum project (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)
A PostgreSQL driver reading DATABASE_URL at runtime
A bucket from
ample bucket createwith credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, databases:read, buckets:read
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
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.
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
- 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
- Axum pattern fixture. Verified private file access on Axum.
What it doesn’t cover
- Verified on the ubuntu-24.04 template at s-1vcpu-2gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.