### Host Reporting Dashboard with Spring Boot: File Attachments

Deploy a reporting dashboard 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). Not separately tested: your upload UI, allowed types, size limits and virus scanning; treat the reporting dashboard-specific behavior as your application code.

#### Representative Queries
- Host reporting dashboard with Spring Boot: file attachments
- Where can I host Reporting dashboard built with Spring Boot?
- I need a restricted upload flow, file validation and record-to-object linkage.

#### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

#### 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.

#### 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**  
   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 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=...`
5. **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 --kind build` then `--kind runtime`.  
   `ample logs --kind build`

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **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, monthly amount $5.00
  - Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.00
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

#### 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 reporting dashboard itself (your upload UI, allowed types, size limits and virus scanning) is application code and was not separately tested.

#### Next Actions
1. **Browse the catalog index**  
   Operation: `GET /v1/catalog`
2. **Search published recipes by intent, stack and constraints**  
   Operation: `POST /v1/catalog/search`  
   Body: {"limit":5,"query":"Host reporting dashboard with Spring Boot: file attachments"}
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   Operation: `POST /v1/catalog/plan`

### Evidence Summary
1. **Canary Run**  
   Summary: Spring Boot pattern fixture deployed on Ample; checks passed for browser-file-uploads and configuration-secrets.
   Observed At: 2026-09-21T02:34:39Z
   Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)

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

#### Framework
Spring Boot

#### Workload
Reporting dashboard

#### Execution Status
Ready

#### Release Status
Published