Configure S3-compatible access for Nuxt · Ample Computer
Framework operation
Configure S3-compatible access for Nuxt
Object storage client for a Nuxt app on Ample. Verified on Nuxt: 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: nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
- A Nuxt project (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template)
- A bucket from
ample bucket createwith credentials passed as encrypted S3_* environment variables - An Ample account token with servers:write, buckets:read
Exact tested configuration
- build
npm run build --if-present - install
npm install - runtime
node - sizes
1vcpu-1gb - start
npm run start - template
node-22
Steps
Build and start. nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template; the server must bind 0.0.0.0 on PORT.
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=...
- Verify. Fetch the live URL and /api/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 nuxt patterns”
✓ browser-file-uploads check from the example· http get/api/p/browser-file-uploads → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
Nuxt pattern fixture deployed on Ample (nuxt build then node .output/server/index.mjs (reads HOST and PORT) 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
- Nuxt pattern fixture. Verified object storage client on Nuxt.
What it doesn’t cover
- Verified on the node-22 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-urlreturns presigned upload URLs.