page:recipes:project tracker:quarkus:private attachments

Host project tracker with Quarkus: private attachments

Deploy a project tracker built with Quarkus 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 Quarkus: 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). Not separately tested: your identity integration and role assignments; treat the project tracker-specific behavior as your application code.

Representative Queries

• Host project tracker with Quarkus: private attachments
• Where can I host Project tracker built with Quarkus?
• I need attachment metadata, access checks and a tested private object access path.

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

• Build and start
  ./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.port read from PORT. The server must bind 0.0.0.0 on PORT.

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

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

• 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=...

• 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 --kind buildthen--kind runtime.
ample logs --kind build

Examples

• Quarkus pattern fixture
  • Description: Multi-pattern Quarkus app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  • Source Reference: tests/deploy-canaries/quarkus-patterns

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Quarkus major versions are not verified.
• The project tracker itself (your identity integration and role assignments) 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.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• 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
     • Monthly Amount: 5.0
  2. Managed PostgreSQL database:
     • Size: s-1vcpu-1gb
     • Quantity: 1.0
     • Monthly Amount: 5.0
• 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.