# Configure S3-compatible access for Quarkus

Object storage client for a Quarkus app on Ample. Verified on Quarkus: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=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`.

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

- [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 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`)

- A bucket from `ample bucket create` with credentials passed as encrypted S3_* environment variables

- An Ample account token with `servers:write`, `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` 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. **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.

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

3. **Verify.** Fetch the live URL and `/p/browser-file-uploads` on the example; on failure read the build and runtime logs.
   
   ```sh
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL · `http get/` → “ample canary quarkus patterns”  
✓ browser-file-uploads check from the example · `http get/p/browser-file-uploads` → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
   Quarkus pattern fixture deployed on Ample (`./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`); for this guide: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=ok).

## Tested examples

- **Quarkus pattern fixture.** Verified object storage client on Quarkus.

## What it doesn’t cover

- Verified on the jvm-21 template at `s-1vcpu-2gb`.
- 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.
