page:guides:quarkus:private file access

Enforce private-file authorization for Quarkus

Summary

Private file access for a Quarkus app on Ample. Verified on Quarkus: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). 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.

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.

Create the bucket and pass its credentials

Create it once with ample bucket create, then pass endpoint, region, bucket and keys with --env; use path-style addressing.
ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

Authorize before touching storage

Return 401 for unauthenticated requests and 403 for the wrong role; keep the bucket unpublished and stream objects through the app.

Verify

Fetch the live URL and /p/private-document-library on the example; on failure read the build and runtime logs.
ample logs --kind build

Prerequisites

Examples

Quarkus pattern fixture

Description: Verified private file access on Quarkus.
Source Reference: tests/deploy-canaries/quarkus-patterns

Success Checks

Limitations

Cost Estimate

Evidence Summary

MCP Binding

Unknowns

Formats

Next Actions