This guide covers the optional organisation service. Configuration, console and API paths refer to your Lolly Work instance. The packaged console keeps its release-matched copy of this guide.
Connect a private bucket on AWS S3, MinIO, Ceph RGW or another S3-compatible store, and its objects appear in the Lolly Work catalog for the groups you choose. The objects stay private: Lolly Work signs every request afresh and streams the file. It never writes to the bucket.
Leaving a DAM for a library you host? Follow the self-hosting strategy with S3 storage.
Lolly Work's writable blobs.driver: "s3" is the destination for materialized copies, with its own credential in LW_BLOBS_S3_CREDENTIAL. Sending finished exports to a bucket is a separate S3 delivery destination, with its own credential too.
What you need from the store
- A read-only access key pair scoped to the bucket, and to the prefix if you set one. On AWS, an IAM user or role with a minimal policy:
{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": ["s3:GetObject", "s3:ListBucket"], "Resource": ["arn:aws:s3:::acme-brand", "arn:aws:s3:::acme-brand/brand/*"] }] }
On MinIO or Ceph, a read-only user or policy over the bucket. Do not grant write or delete.
- The bucket name and the region. SigV4 needs a region even where MinIO ignores the value.
- The endpoint URL for an S3-compatible store.
Credential shape
One string: the access key id and the secret access key joined by a colon. Every bucket needs one, even for a dry run.
"<accessKeyId>:<secretAccessKey>"lw providers credential acme-s3 # prompts for the "<key>:<secret>" stringinstance.json / lw providers add
{
"id": "acme-s3",
"kind": "s3",
"label": "Acme MinIO",
"options": { "bucket": "acme-brand", "region": "us-east-1", "endpoint": "https://minio.internal:9000", "prefix": "brand" },
"exposure": { "groups": ["design"], "tier": "reference" }
}| Option | What it does |
|---|---|
bucket (required) | The bucket to federate. |
region | Default us-east-1. |
endpoint | The store's URL. Absent means AWS virtual-hosted addressing. |
prefix | Federate only the keys under this prefix. |
The first folder below the prefix, or below the bucket root when there is no prefix, becomes each object's section, which exposure.includeSections can scope on.
Verify
lw providers preview --kind s3 --options '{"bucket":"acme-brand","region":"us-east-1"}'
lw providers health acme-s3s3 list 403 means one of two things: the policy lacks s3:ListBucket on the bucket ARN (separate from the /* object ARN), or the secret or region is wrong. The driver reports only the HTTP status, not the S3 error code.
Notes / limits
- No server-side search.
- No presigned links in the catalog. A request for an object outside the configured prefix is refused.
- Zero dependencies. The driver signs requests with its own SigV4 code, with no AWS SDK.