Configure S3-compatible access for NestJS · Ample Computer

Configure S3-compatible access for NestJS

Object storage client for a NestJS app on Ample. Verified on NestJS: 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: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template.

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. npm install, nest build (TypeScript) then node dist/main.js on the node-22 template; 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=...
  1. 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 nestjs 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
    NestJS pattern fixture deployed on Ample (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template); 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

What it doesn’t cover