MinIO (S3)

briq_run({
  recipe: "minio",
  params: {
    "bucket": "app",
    "size": "small",
    "diskGb": 5
  },
  wait: true
})

curl -X POST https://api.briq.cloud/v1/briqs \
  -H "Authorization: Bearer $BRIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "recipe": "minio",
    "params": {
      "bucket": "app",
      "size": "small",
      "diskGb": 5
    },
    "wait": true
  }'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "S3_ENDPOINT": "…" }, … }

# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
  -H "Authorization: Bearer $BRIQ_API_KEY"

When to use it

• Your code uploads to S3 and you want a real bucket without AWS credentials.
• Presigned URLs, multipart uploads or bucket policies must behave like S3.

The bucket is created at boot. Outputs follow AWS SDK naming.

Tips

• Path style: set forcePathStyle: true (AWS SDK v3) or s3ForcePathStyle (v2).
• Region us-east-1, as in the outputs.
• Console for a human: briq_run({ recipe: "minio", expose: "private" }) returns its URL.
• Presigned URLs carry the private host. If a browser must use them, expose port 9000 instead of the console and sign against that URL: a briq has one URL, and moving it to another port restarts the briq.
• Image: pgsty/minio, the maintained community build, since MinIO stopped publishing community images.
• More storage: the volume starts small; pass diskGb, e.g. params: { diskGb: 50 }. Set it when the briq is created, and it counts toward your plan's disk.