Host admin dashboard with Spring Boot: tenant-scoped workspaces

Deploy a admin dashboard built with Spring Boot on Ample using the multi-tenant relational data 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. Verified on Spring Boot: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the admin dashboard-specific behavior as your application code.

Summary

• Framework: Spring Boot
• Workload: Admin dashboard
• Release Status: Published
• Support Status: Verified
• Execution Status: Ready
• Docs Only: false

Representative Queries

1. Host admin dashboard with Spring Boot: tenant-scoped workspaces
2. Where can I host Admin dashboard built with Spring Boot?
3. I need an explicit tenant model and application-enforced tenant isolation tests.

Resource Requirements

• Compute
• Postgres

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.

Prerequisites

1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. An Ample account token with servers:write, databases:read.

Tested Configuration

• Template: jvm-21
• Runtime: java
• Size: s-1vcpu-2gb
• Build: ./mvnw -q -DskipTests package
• Start: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

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
   • Body: The fixture's module implements multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Deploy
   • Command: ample deploy . --name --public
4. Verify
   • Command: ample logs --kind build

Success Checks

1. app responds on its public URL
   • Kind: http_get
   • Path: /
   • Expect: ample canary spring boot patterns
2. multi-tenant-relational-data self-test
   • Kind: http_get
   • Path: /p/multi-tenant-relational-data
   • Expect: tenant_isolation=ok

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 admin dashboard itself (your tenant model, membership and per-tenant authorization) 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.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server (size: s-1vcpu-1gb; quantity: 1.0; monthlyAmount: 5.0)
  • Managed PostgreSQL database (size: s-1vcpu-1gb; quantity: 1.0; monthlyAmount: 5.0)
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

1. Browse the catalog index
   • Method: GET
   • Relative Path: /v1/catalog
2. Search published recipes by intent, stack and constraints
   • Method: POST
   • Relative Path: /v1/catalog/search
3. Prepare a side-effect-free deployment plan for an authorized project
   • Method: POST
   • Relative Path: /v1/catalog/plan
4. Read the existing agent authentication 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 Multi-tenant relational data
   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data
8. Browse Deploy web app
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app