Component

core/storage/s3-object-store

One object-storage bucket reached over the S3 API with an access key. A consumer points its S3 client at the published endpoint, signs for the published region and reads the published bucket, which is the bucket the store holds, so a consumer naming a bucket of its own checks it against this one. A consumer holds the key it presents on its own connection. The two key slots are a self-hosted server's own account, which SeaweedFS requires; a managed service issues its keys to its own principals outside the build, and its realization refuses an attached slot by name. Reach for it where the consumer speaks the S3 API with an access key, wherever it runs; and for core/storage/gcs where it uses Google's client libraries with a Google identity, or needs a setting only Cloud Storage has. Realized on Amazon S3, in an AWS account, by terraform/s3-object-store-amazon-s3 through Terraform and by cloudformation/s3-object-store-amazon-s3 in a CloudFormation stack: every public access is blocked, ACLs are disabled, and a consumer brings an IAM principal's access key. Realized on Google Cloud Storage, in a Google Cloud project, by terraform/s3-object-store-gcs, over its XML API: the bucket is never public, a consumer brings a Cloud Storage HMAC key, and an object ACL is refused under uniform bucket-level access. Realized on SeaweedFS, run in a cluster by helm/s3-object-store or on a Compose host by compose/s3-object-store with nothing else in place: the server creates the bucket, serves plain HTTP, and a consumer brings the key pair the slots hold.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:9548eb7db5f04218d18e6d0ac1a9b4b97da962f9211852e927b758b6cd82b46c
Published
2026-11-10T10:14:08Z
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:33587ea3c49984c9cec47ab460d42040455e6f3f7b99e71c4abd6e649cb3d658

Reference at this version

oci://hub.aggrega.ai/component/core/storage/s3-object-store:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
bucketstring—yesName of the bucket the store holds, published as `bucket`. Each realization refuses a name its service does not take, naming the rule; on Cloud Storage a bucket name is unique across the whole service, and on Amazon S3 across its partition, and on both it is publicly visible, so it carries nothing confidential.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
regionstring—noWhere the bucket is placed, published as `region`, the region a consumer's S3 client signs for. There is no default: a managed realization halts without one, because where the data lives is the operator's choice. On Amazon S3 it is the bucket's Region code, such as eu-west-1, and a CloudFormation stack is held to that Region. On Cloud Storage it is the bucket's location — a region such as europe-west1, a dual-region such as EUR4 or a multi-region such as EU — and Cloud Storage accepts any region in a signature. SeaweedFS reads none, so its realizations halt when it is set and publish us-east-1, which S3 clients read from a server reporting no region.
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
bucketstring—yesThe bucket the store holds. A consumer reads its objects from this bucket; one that names a bucket of its own checks it against this one.
regionstring—noThe region a consumer's S3 client signs its requests for: on a managed service the bucket's own location as the Release names it, and on SeaweedFS us-east-1, since the server reads none.
endpointstring—yesBase URL of the S3 API — scheme, host and, where it is not the scheme's default, port — the address a consumer points its S3 client at. The scheme is the one the store is reached over, so a consumer takes the address as published rather than assuming http.
hoststring—yesHost name of the S3 API. A consumer that composes its own address dials this name together with `port`; one that does not reads `endpoint` instead.
portinteger—yesTCP port the S3 API accepts requests on, the one `endpoint` names or implies.
protocolstring—noWire protocol the published address speaks — `s3`, so a consumer knows to reach it with an S3 client rather than a plain HTTP one.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

SlotSelectorRequiredInjectSensitiveDescription
access_key_idfeature.aggrega.ai/kind=secretnoenvyesAccess key identifier of the store's own account, for a store that takes a key pair of its own: SeaweedFS takes the pair as its S3 identity, and its realizations halt when this slot is empty. A managed service issues its keys to its own principals outside the build, so the Amazon S3 and Cloud Storage realizations refuse an attachment here by name. A consumer presents its own key on its own connection.
secret_access_keyfeature.aggrega.ai/kind=secretnoenvyesSecret access key of the store's own account, the pair of access_key_id, for a store that takes a key pair of its own: SeaweedFS takes the pair as its S3 identity, and its realizations halt when this slot is empty. A managed service issues its keys to its own principals outside the build, so the Amazon S3 and Cloud Storage realizations refuse an attachment here by name. A consumer presents its own key on its own connection.

Self-inject allowlist

env

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

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy