Host asset library with Spring Boot: file attachments · Ample Computer

Host asset library with Spring Boot: file attachments

Deploy an asset library built with Spring Boot on Ample using the browser file uploads pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Spring Boot: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). The asset library-specific behavior (your upload UI, allowed types, size limits and virus scanning) is your application code on that verified basis.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

build./mvnw -q -DskipTests package

runtimejava

sizes-1vcpu-2gb

startjava -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

templatejvm-21

Steps

  1. 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. The server must bind 0.0.0.0 on PORT.

  2. Implement the pattern on PostgreSQL. The fixture's module implements browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

  3. Wire object storage. Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

  4. Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

   $ 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 the pattern self-test route(s) (/p/browser-file-uploads) from the example; then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.
   $ 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 self-test · http get/p/browser-file-uploads → "reject=ok upload=ok linked=ok"

Evidence

  1. November 6, 2026 · canary run
    Spring Boot pattern fixture deployed on Ample (./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); checks passed for browser-file-uploads and configuration-secrets. Pattern proof: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

  2. November 6, 2026 · canary run
    The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover