page:guides:echo:object client

Configure S3-compatible access for Echo

Summary

Object storage client for a Echo app on Ample. Verified on Echo: 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: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build).

Representative Queries

• Configure S3-compatible access for Echo
• Where can I host Configure S3-compatible access built with Echo?
• I need exact S3 endpoint, credentials, operation requirements and an upload/download verification.

Resource Requirements

• primitive:compute
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Prerequisites

• A Echo project (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
• A bucket from ample bucket create with credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, buckets:read

Tested Configuration

• Template: ubuntu-24.04
• Runtime: go
• Size: s-1vcpu-1gb
• Build: CGO_ENABLED=0 go build -o app ./...
• Start: ./app

Workflow Steps

1. Build and start: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build); 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.

   Command: ample deploy . --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.

   Command: ample logs --kind build

Examples

• Echo pattern fixture: Verified object storage client on Echo.

Success Checks

• App responds on its public URL.
• Browser-file-uploads check from the example.

Limitations

• Verified on the ubuntu-24.04 template at s-1vcpu-1gb; other sizes and Echo major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Evidence Summary

• Canary Run: Echo pattern fixture deployed on Ample (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build)).

Next Actions

1. Browse the catalog index: GET /v1/catalog
2. Search published recipes: POST /v1/catalog/search
3. Prepare deployment plan: POST /v1/catalog/plan