page:recipes:admin dashboard:spring boot:public profiles

Host Admin Dashboard with Spring Boot: Public Profile Assets

Summary

Deploy an admin dashboard built with Spring Boot on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the admin dashboard-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute
    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
    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
    Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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

Prerequisites

Workflow 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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 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. Publish only the bucket that serves public assets and reference its CDN URL.

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

    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
    Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

    ample logs --kind build

Examples

Success Checks

  1. App responds on its public URL

    • Kind: http_get, Path: /, Expect: ample canary spring boot patterns

  2. Public-media-library self-test

    • Kind: http_get, Path: /p/public-media-library, Expect: a CDN URL whose content is served publicly

  3. Private-document-library self-test

    • Kind: http_get, Path: /p/private-document-library, Expect: private=ok (with ?role=owner; 401 without, 403 for viewer)

Limitations

Cost Estimate

Evidence Summary

  1. Canary Run

    • Summary: 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, private-document-library and configuration-secrets. Pattern proof: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role).
    • Observed At: 2026-09-21T02:34:39Z
    • Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
    • Expires At: 2027-03-20T02:34:39Z

  2. Canary Run

    • Summary: The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.
    • Observed At: 2026-09-20T22:49:19Z
    • Implementation Revision: af6f45adea26-dirty (CLI af6f45a)
    • Expires At: 2027-03-19T22:49:19Z

Unknowns

Formats

Next Actions

  1. Browse the Catalog Index

    • Method: GET
    • Relative Path: /v1/catalog

  2. Search Published Recipes

    • Method: POST
    • Relative Path: /v1/catalog/search
    • Parameters: {"body":{"limit":5,"query":"Host admin dashboard with Spring Boot: public profile assets"}}

  3. Prepare a Deployment Plan

    • Method: POST
    • Relative Path: /v1/catalog/plan
    • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:admin-dashboard:spring-boot:public-profiles","recipeRevision":"r1"}}

  4. Read Existing Auth Setup

    • Method: GET
    • Relative Path: /mcp/setup

  5. Browse Admin Dashboard

    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Aadmin-dashboard

  6. Browse Spring Boot

    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-spring-boot

  7. Browse Public Image Delivery

    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Apublic-image-delivery

  8. Browse Deploy Web App

    • Method: GET
    • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app