page:recipes:product catalog:spring boot:product media

Host product catalog with Spring Boot: public product media

Summary

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. Not separately tested: your media processing, object layout and cache policy; treat the product catalog-specific behavior as your application code.

Representative Queries

• Host product catalog with Spring Boot: public product media
• Where can I host Product catalog built with Spring Boot?
• I need product-to-object mappings and a tested public media delivery path.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage
• primitive:cdn

Infrastructure Requirements

1. Compute
   Status: verified
   Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. Postgres
   Status: verified
   Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

3. S3-compatible object storage
   Status: verified
   Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

4. CDN
   Status: verified
   Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Prerequisites

• 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 create with 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.

Workflow Steps

1. Build and start
   Command: ./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
   Description: 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.

3. Wire object storage
   Description: 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.

4. Deploy
   Command: ample deploy . --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=...

5. Verify
   Command: ample logs --kind build

Success Checks

1. App responds on its public URL
   Expected: ample canary spring boot patterns

2. Public-media-library self-test
   Expected: a CDN URL whose content is served publicly

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Spring Boot major versions are not verified.
• The product catalog itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

Cost Estimate

• Currency: USD
  Monthly Amount: 10.0
  Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  1. App server: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  2. Managed PostgreSQL database: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0

Examples

• Spring Boot pattern fixture
  Description: Multi-pattern Spring Boot app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  Source Ref: tests/deploy-canaries/spring-boot-patterns

Next Actions

• Browse the catalog index
  Method: GET
  Relative Path: /v1/catalog
• Search published recipes by intent, stack and constraints
  Method: POST
  Relative Path: /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project
  Method: POST
  Relative Path: /v1/catalog/plan
• Read the existing agent authentication setup
  Method: GET
  Relative Path: /mcp/setup
• Browse Product catalog
  Method: GET
  Relative Path: /v1/catalog/nodes/workload%3Aproduct-catalog
• Browse Spring Boot
  Method: GET
  Relative Path: /v1/catalog/nodes/stack%3Aframework-spring-boot
• Browse Public media library
  Method: GET
  Relative Path: /v1/catalog/nodes/pattern%3Apublic-media-library
• Browse Deploy web app
  Method: GET
  Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app

Links

• HTML Format
• Markdown Format
• JSON Format