Configure S3-compatible access for Axum

Summary

Object storage client for a 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.

Infrastructure requirements

• S3-compatible object storage: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

Prerequisites

• A 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 create with credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, buckets:read

Exact tested configuration

• template: ubuntu-24.04
• runtime: rust
• size: s-1vcpu-2gb
• build: cargo build --release
• start: ./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/\.d$//')

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. 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

Tested examples

• Axum pattern fixture (tests/deploy-canaries/axum-patterns): Verified object storage client on Axum.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary axum patterns)
• browser-file-uploads check from the example (/p/browser-file-uploads on the live URL, expect see the pattern fixture checks)

Limitations

• Verified on the ubuntu-24.04 template at s-1vcpu-2gb; other sizes and Axum major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• PutObject and GetObject with path-style addressing are verified; other S3 operations are not.

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

Verification evidence

• canary_run on 2026-09-21T02:46:37Z at revision 1d28ae0-dirty (CLI 0.1.21): 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). (expires 2027-03-20T02:46:37Z)

Last verified: 2026-09-21T02:46:37Z

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, buckets:read.