page:guides:quarkus:configuration secrets

Configure environment and secrets for Quarkus

Summary

Configuration and secrets for a Quarkus app on Ample. Verified on Quarkus: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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.

Representative Queries

• Configure environment and secrets for Quarkus
• Where can I host Configure environment and secrets built with Quarkus?
• I need a tested app-configuration delivery method and secret-handling guidance; platform injection/rotation is not assumed.

Required Resources

• Compute: Runs in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

Prerequisites

• A Quarkus project (./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)
• An Ample account token with servers:write

Workflow Steps

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

2. Pass values on deploy
   Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.
   Command: ample deploy . --name --public --env MY_SECRET=...

3. Verify
   Fetch the live URL and /p/configuration-secrets on the example; on failure read the build and runtime logs.
   Command: ample logs --kind build

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)

Examples

• Quarkus pattern fixture: Verified configuration and secrets on Quarkus. Source Ref: tests/deploy-canaries/quarkus-patterns

Success Checks

• App responds on its public URL
• Configuration-secrets check from the example

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb; other sizes and Quarkus major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.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, monthly amount 5.0

Evidence Summary

• Kind: Canary run
• Summary: Quarkus pattern fixture deployed on Ample.
• Observed At: 2026-09-21T00:35:31Z

Next Actions

• Action 1: Browse the catalog index
• Action 2: Search published recipes by intent, stack and constraints
• Action 3: Prepare a side-effect-free deployment plan for an authorized project
• Action 4: Read the existing agent authentication setup
• Action 5: Browse Quarkus
• Action 6: Browse Configure deployment
• Action 7: Browse Public web service

Formats:

• HTML
• Markdown
• JSON