# Configure S3-compatible access for Phoenix

Object storage client for a Phoenix app on Ample. Verified on Phoenix: 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: 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

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- A Phoenix project (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)

- 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

- 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`
- template: elixir-1.18

## 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=...
   ```

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

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary phoenix patterns”  
✓ browser-file-uploads check from the example · http get/p/browser-file-uploads → “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: 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

- **Phoenix pattern fixture.** Verified object storage client on Phoenix.

## What it doesn’t cover

- Verified on the elixir-1.18 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
