page:recipes:inventory manager:quarkus:report exports
Host Inventory Manager with Quarkus: Downloadable Reports
Deploy an inventory manager built with Quarkus on Ample using the generated downloads 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.
Summary
Verified on Quarkus: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy, and entitlement model; treat the inventory manager-specific behavior as your application code.
Representative Queries
- Host inventory manager with Quarkus: downloadable reports
- Where can I host Inventory manager built with Quarkus?
- I need an export query, generated artifact retention, and authorized download flow.
Resource Requirements
- Compute
- PostgreSQL
- S3-compatible object storage
Infrastructure Requirements
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.
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.
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.
Prerequisites
- A Quarkus project that builds and starts with the documented commands.
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variables. - An Ample account token with servers:write, databases:read, buckets:read.
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.Implement the Pattern on PostgreSQL
The fixture's module implements generated downloads.Wire Object Storage
Create the bucket(s) then pass endpoint, region, bucket, and keys as --env values.Deploy
Run the synchronous deploy once and read the result.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) from the example; then run your own checks.ample logs --kind build
Example
Quarkus Pattern Fixture
- Description: Multi-pattern Quarkus app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
- Source Reference: tests/deploy-canaries/quarkus-patterns
Success Checks
- app responds on its public URL
- generated-downloads self-test
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 inventory manager itself was not separately tested; the pattern checks are what was verified.
Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Note: Always-on monthly price of the tested sizes.
- App Server: s-1vcpu-1gb, Monthly Amount: 5.0
- Managed PostgreSQL Database: s-1vcpu-1gb, Monthly Amount: 5.0
Evidence Summary
- Canary Run: Quarkus pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
- Observed At: 2026-09-21T00:35:31Z
- Expires At: 2027-03-20T00:35:31Z
- Canary Run: The same Quarkus app deployed with a --release-command migration; the marker it created was readable after activation.