object client.md

Configure S3-compatible access for Next.js

Summary

Configure S3-compatible access for a Next.js app on Ample. Create a bucket with ample bucket create, pass its endpoint, region, bucket name and keys as encrypted environment variables, and use @aws-sdk/client-s3 inside a dynamic route handler with forcePathStyle: true. The app writes and reads objects through the S3-compatible endpoint; the bucket stays private.

Infrastructure requirements

Prerequisites

Exact tested configuration

Steps

  1. Create the bucket. Create it once and keep the issued credentials out of the repository.
   ample bucket create --name <bucket-name>
  1. Configure the client with path-style addressing. Use @aws-sdk/client-s3 inside a dynamic route handler with forcePathStyle: true; virtual-host addressing is not verified.
  2. Deploy with the credentials as encrypted env. Pass the five S3_* variables with --env; they are stored encrypted and reused on redeploys.
   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=...
  1. Test through the app. Expose a route (/api/storage) that writes then reads an object and reports s3=ok.
  2. Verify. Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.
   ample logs <deployment_id> --kind build

Tested examples

Success checks

Limitations

Cost estimate

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

Compute only. Buckets are allocation-priced per quota and capped by the plan; see ample usage.

Verification evidence

Last verified: 2026-09-20T01:13:26Z

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-20T01:55:48.667900+00:00 at revision 199ff1dfd526, binding state current, required scopes: servers:write, buckets:read.