Configure S3-compatible access for Next.js · Ample Computer

Configure S3-compatible access for Next.js

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.

What it runs on

You need

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 (path-style addressing).

  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

How it was checked

✓ object write and read succeed · http get/api/storage → “s3=ok”

Evidence

  1. November 5, 2026 · canary run Next.js route handler using @aws-sdk/client-s3 with injected bucket credentials: PutObject then GetObject returned s3=ok at request time.

  2. November 5, 2026 · canary run ample bucket create issued credentials; PutObject and GetObject succeeded through the public S3 endpoint; publish exposed the object at its public URL with an ETag; unpublish and delete cleaned up.

Tested examples

What it doesn’t cover