Host product catalog with Spring Boot: public product media · Ample Computer
Host product catalog with Spring Boot: public product media
Deploy a product catalog built with Spring Boot on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on Spring Boot: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. The product catalog-specific behavior (your media processing, object layout and cache policy) is your application code on that verified basis.
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.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.CDNverified
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
You need
- A Spring Boot project that builds and starts with the documented commands (./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)
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*) - An Ample account token with servers:write, databases:read, buckets:read
Exact tested configuration
build: ./mvnw -q -DskipTests package
runtime: java
sizes: 1vcpu-2gb
start: 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, 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.
Implement the pattern on PostgreSQL. The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
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. Publish only the bucket that serves public assets and reference its CDN URL.
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=... --env CDN_PUBLIC_URL=...
- Verify. Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. On failure read
ample logs <deployment_id> --kind buildthen--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”
✓ public-media-library self-test · http get/p/public-media-library → “a CDN URL whose content is served publicly”
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, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT); checks passed for public-media-library and configuration-secrets. Pattern proof: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.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
- Spring Boot pattern fixture. Multi-pattern Spring Boot app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
- Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture.
- The pattern checks verified the platform side; the product catalog itself (your media processing, object layout and cache policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- 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. - The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.