Recipe
s3-object-store
An S3-compatible object store on a Compose host: SeaweedFS 4.48, Apache-2.0, from its project's published chrislusf/seaweedfs image, run by the compose provider's Workload synthesis as one weed server process — master, volume server, filer and S3 gateway — with a named volume for its data and the S3 port published on the host. An init service creates the bucket values.bucket names before the server serves, and leaves an existing one as it is. Reach for it where the store runs on a Compose host with nothing else in place; for helm/s3-object-store in a Kubernetes cluster; for terraform/s3-object-store-amazon-s3 or cloudformation/s3-object-store-amazon-s3 in an AWS account; and for terraform/s3-object-store-gcs in a Google Cloud project. The access_key_id and secret_access_key slots are the server's S3 account, and both are required here: each value arrives on the inject pipe under AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY and is written into the service's environment as delivered, so a Compose variable reference such as ${S3_SECRET_ACCESS_KEY} keeps the key out of the file. An empty slot halts naming it. The server serves plain HTTP on the Compose network and the host; only the S3 gateway listens beyond the container, on its S3 port and the gRPC port beside it, and each refuses a caller without the key. It publishes the bucket, the endpoint http://<service>:8333, its host, port 8333, protocol s3 and region us-east-1, the one S3 clients read from a server reporting none. infra.region, any infra.overrides key and a bucket name SeaweedFS does not take halt naming the key.
Provenance
- Content digest
- sha256:11b73aee8bb6bca4d97a60eb1d076a034d6fae6af860b772bdbb3de0b7d61c47
- Published
- 2026-11-10T10:20:47Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:44548d7460f6650b37b0fc6eedcda61e8b595c02979ba33c863cf1646a619d9b
Reference at this version
oci://hub.aggrega.ai/recipe/compose/s3-object-store:1.0.0- Target
- —
- Implements
- core/storage/s3-object-store:1.0.0
Provides
Deterministic pointer templates this recipe wires for consumers.
| Name | Template |
|---|---|
| bucket | {{ .values.bucket }} |
| region | us-east-1 |
| endpoint | http://{{ .context.instance_id }}:8333 |
| host | {{ .context.instance_id }} |
| port | 8333 |
| protocol | s3 |
Workload
Workload · containers: main
Locals
No locals declared.
Values mapping
No values mapping declared.
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
- implementsimplementscontract compatible
core/storage/s3-object-store:1.0.0
All required outputs are satisfied and every provided output is named in the contract.
Used by
Nothing in the catalog depends on this entity.