Configure S3-compatible access for Axum · Ample Computer
Configure S3-compatible access for Axum
Object storage client for an Axum app on Ample. Verified on Axum: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=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.
Verified November 5, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.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 bucket from
ample bucket createwith credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, buckets:read
Exact tested configuration
- build: cargo build --release
- runtime: rust
- sizes: 1vcpu-2gb
- start: ./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/.d$//')
- template: ubuntu-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=...
- Verify. Fetch the live URL and /p/browser-file-uploads 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”
✓ browser-file-uploads check from the example · http get/p/browser-file-uploads → “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: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=ok).
Tested examples
- Axum pattern fixture. Verified object storage client on Axum.
What it doesn’t cover
- Verified on the ubuntu-24.04 template at s-1vcpu-2gb.
- 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.