Component

core/observability/thanos-store

Thanos Store Gateway, the read side of a Thanos metrics stack. The Store Gateway reads historical metric blocks from an S3-compatible object store and serves them to queriers over its StoreAPI on a gRPC port. The object store it reads from is wired through its `objstore` uses-socket: the endpoint the store publishes gives the S3 endpoint in the object-store configuration, and its scheme whether that connection is plain HTTP or TLS. Credentials reach the process as environment variables through the AWS SDK credential chain rather than being embedded in that configuration, so the rendered configuration carries no secret: the access key's secret half is the connection's `credential`, and its identifier the connection's `credential_id` where one is attached, else the `s3_access_key` value. The Store Gateway keeps only an ephemeral local cache of index data — the object store is the system of record — so it renders as a stateless server. Exports its StoreAPI host, port, and protocol to consumers via the uses topology. The gateway serves its own metrics in the Prometheus format at /metrics on its HTTP port, not the published StoreAPI port, and publishes that address as `metrics_endpoint`.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:d72db93af276a5cf3f877eea9d563e888ed7e96587318aa71688d73fe939f37d
Published
2026-11-10T10:13:20Z
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:c98c2833eb7473faf6e304aa4b848670713311d41b2f33a638f1510c942d5215

Reference at this version

oci://hub.aggrega.ai/component/core/observability/thanos-store:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
s3_access_keystringadminnoS3 access-key identifier presented to the object store where the `objstore` connection carries no `credential_id`; a `credential_id` attached there is presented in its place. Its secret is the `credential` the `objstore` connection carries.
bucketstringthanosnoObject-store bucket the Store Gateway reads metric blocks from. The bucket must be pre-created out of band; the read tier does not provision it. Where the store wired to `objstore` publishes a bucket of its own, this names the same one, or the build halts.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
http_portinteger (min 1024, max 65535)10902noHTTP port serving health and metrics endpoints, reachable in-cluster only.
grpc_portinteger (min 1024, max 65535)10901nogRPC port serving the StoreAPI; queriers connect here.
engine_versionstringv0.42.0noThanos container image tag.
computeobject—no—
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
hoststring—yesIn-cluster DNS name of the Service the gateway serves historical metric blocks on. A query front end adds this name to its store list together with `port`.
portinteger—yesTCP port the store API is served on. It carries the gRPC port an operator set, never the health-and-metrics HTTP port.
protocolstring—noHow the published address is spoken to — `grpc`, so a query front end dials it as a store rather than as an HTTP endpoint.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<http_port>/metrics` on the HTTP port, which is not the published `port`. Empty where the component serves none reachable.

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.

objstore

Selector
component.aggrega.ai/type=resource,component.aggrega.ai/category=storage
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credential_idfeature.aggrega.ai/kind=secretnoenvyesAccess-key identifier the Store Gateway presents to the object store this connection reaches, the identifier half of the pair whose secret half is this connection's credential, supplied as the object-store access key ID via the credential subsystem. It names an account on that store, so it matches whatever the store itself was given. Unattached, the s3_access_key value is presented instead.
credentialfeature.aggrega.ai/kind=secretnoenvyesS3 secret key the Store Gateway presents to the object store this connection reaches, supplied as the object-store secret access key via the credential subsystem. There is no default: the build halts when nothing fills this slot, unless the connection's values set unauthenticated: true.

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.

No attachment slots declared.

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

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