Configure S3-compatible access for Spring Boot · Ample Computer
Configure S3-compatible access for Spring Boot
Object storage client for a Spring Boot app on Ample. Verified on Spring Boot: 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: ./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT.
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 Spring Boot project (
./mvnw -q -DskipTests package(or the Gradle wrapper) producing one application jar, thenjava -jaron the jvm-21 template (Temurin JDK 21) withserver.portread fromPORT)A bucket from
ample bucket createwith credentials passed as encrypted S3_* environment variablesAn Ample account token with
servers:write,buckets:read
Exact tested configuration
build
./mvnw -q -DskipTests packageruntime
javasizes
-1vcpu-2gbstart
java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)template
jvm-21
Steps
Build and start.
./mvnw -q -DskipTests package(or the Gradle wrapper) producing one application jar, thenjava -jaron the jvm-21 template (Temurin JDK 21) withserver.portread fromPORT; the server must bind0.0.0.0onPORT.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
/p/browser-file-uploadson 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 spring boot patterns”
✓ browser-file-uploads check from the example· http get/p/browser-file-uploads → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
Spring Boot pattern fixture deployed on Ample (./mvnw -q -DskipTests package(or the Gradle wrapper) producing one application jar, thenjava -jaron the jvm-21 template (Temurin JDK 21) withserver.portread fromPORT); 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
- Spring Boot pattern fixture. Verified object storage client on Spring Boot.
What it doesn’t cover
- Verified on the jvm-21 template at
s-1vcpu-2gb. - 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.