# Host Recruiting Tracker with Spring Boot: Private Attachments

Deploy a recruiting tracker built with Spring Boot on Ample using the private document 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. Verified on Spring Boot: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The recruiting tracker-specific behavior (your identity integration and role assignments) is your application code on that verified basis.

**Verified**: November 6, 2026

## What It Runs On

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  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](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## 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 create` with its credentials passed as encrypted S3_* environment variables

- An Ample account token with permissions: `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

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 private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). 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 needs an answer first). Re-running with no change is a no-op.

```sh
   $ 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=...
   ```

5. **Verify.**  
   Fetch the live URL and the pattern self-test route(s) (`/p/private-document-library`) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```sh
   $ ample logs <deployment_id> --kind build
   ```

## How It Was Checked

✓ app responds on its public URL · `http get/` → “ample canary spring boot patterns”  
✓ private-document-library self-test · `http get/p/private-document-library` → “private=ok (with ?role=owner; 401 without, 403 for viewer)”

## Evidence

1. 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 private-document-library and configuration-secrets. Pattern proof: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

2. 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 private document 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 recruiting tracker itself (your identity integration and role assignments) 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-url` returns presigned upload URLs.
