Component

core/datastore/memcached

A Memcached in-memory key-value cache. Non-persistent by design: entries live in memory and are not durably stored, so the component renders as a stateless workload rather than a stateful one and declares no storage. Realized by a Helm Recipe (Workload synthesis to native Kubernetes resources), a Compose Recipe (local development), on Amazon ElastiCache and on Google Cloud Memorystore for Memcached. Exports its host and port to consumers via the uses topology. Reach for terraform/memcached-elasticache, or cloudformation/memcached-elasticache in a CloudFormation stack, where the cache is an ElastiCache service in the operator's AWS account; each halts naming each value ElastiCache cannot apply, and takes infra.engine_version as a full version ElastiCache offers, such as 1.6.22. Reach for terraform/memcached-memorystore where the cache is a Memorystore instance in the operator's Google Cloud project, whose VPC network has a private services access connection: one node, its address published, with no TLS and no authentication. Google is deprecating that service, which it shuts down on January 31, 2029. Encrypted client connections are an operator setting, `infra.client_tls`, off by default. Turned on, the cache serves TLS alone on its port and publishes `protocol` `memcached-tls`, so a consumer reading `protocol` learns that it must connect over TLS. On Kubernetes the server presents the Secret attached to the `server_certificate` slot, mounted as files, and asks no client for a certificate; ElastiCache presents a certificate AWS issues; the Compose and Memorystore realizations refuse the setting by name.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:a5e291f6d6b700bd97ba6c44d3c742e267b8e96552fb51763d9c2138225f389e
Published
2026-11-10T10:10:48Z
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:502454f8d9cd8280fa6c62043b00dc21c1134dc6503944e6d5d28305eb284630

Reference at this version

oci://hub.aggrega.ai/component/core/datastore/memcached:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
userstringcachenoSASL authentication username. No realization reads it, since every one halts on an attached password.
memory_limitinteger (min 1)—noMaximum memory for item storage, in megabytes (the memcached -m flag). Omit to use the memcached default (64). ElastiCache fixes it by the node type, so its realizations halt on it. Memorystore sets the limit to the node's memory, so terraform/memcached-memorystore sizes the node by it, 1024 to 262144 in whole GB, 1024 when omitted.
max_connectionsinteger (min 1)—noMaximum number of simultaneous connections (the memcached -c flag). Omit to use the memcached default (1024). ElastiCache and Memorystore fix it at 65000, so their realizations halt on it.
threadsinteger (min 1)—noNumber of worker threads (the memcached -t flag). Omit to use the memcached default (4). ElastiCache sets it by the node type, so its realizations halt on it. Memorystore sets the thread count to the node's vCPUs, so terraform/memcached-memorystore sizes the node by it, 1 to 32, 1 when omitted.
max_item_sizestring—noMaximum size of a single item (the memcached -I flag, e.g. 1m). Omit to use the memcached default (1m). ElastiCache takes it as a parameter, a whole multiple of 512k, and Memorystore too, up to 128m.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
portinteger (min 1024, max 65535)11211noServer listen port. Most operators should omit this and let the Recipe assign the default (11211). Memorystore serves 11211 alone, so terraform/memcached-memorystore halts on any other value.
client_tlsbooleanfalsenoServe client connections over TLS alone. Off by default, which serves plaintext and renders exactly as a cache without the setting. On, the server serves TLS on `port`, presents the certificate attached to `server_certificate` (required while this is on), requests no client certificate, and the published `protocol` is `memcached-tls`. Served by the `memcached` Kubernetes realization; the Compose realization refuses it. On ElastiCache it turns on the service's in-transit encryption, from Memcached 1.6.12, whose certificate AWS issues and clients trust without a `server_ca`. Memorystore offers no encryption in transit, so its realization refuses it.
engine_versionstring1.6-alpinenoMemcached container image tag. Selects the image tag on container targets. The ElastiCache realizations read the version number the value begins with as the engine version, which ElastiCache takes in full, so the default halts there and the Release sets a version it offers, such as 1.6.22. Memorystore runs 1.5.16 and 1.6.15, the one release of each line it offers, so terraform/memcached-memorystore reads 1.6, the default's, as 1.6.15.
replicasinteger (min 1)1noNumber of cache nodes the cache runs; on ElastiCache, the cluster's node count. Memorystore gives each node an address of its own, and this component publishes one, so terraform/memcached-memorystore runs one node and halts above 1.
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—yesAddress a consumer puts in its client's server list, together with `port`: the in-cluster DNS name of the Service fronting the cache on Kubernetes, and on ElastiCache a pointer string Terraform or CloudFormation resolves to the cluster's configuration endpoint, on Memorystore a pointer Terraform resolves to the node's address, or the DNS name the Release sets in infra.overrides.host instead, so a consumer on another target receives an address it can resolve.
portinteger—yesTCP port the cache accepts connections on. It follows the port an operator set in the Release, or the one port the service serves on Memorystore, so a consumer reads it rather than assuming 11211.
protocolstring—noWire protocol the published address speaks — `memcached`, which is what a consumer selects a client for, while `infra.client_tls` is off, and `memcached-tls` while it is on, when the address accepts TLS connections alone. A client that reads only `host` and `port` reads this key too to learn that TLS is required: a plaintext client reaching a TLS listener fails its handshake and exchanges no command.

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
passwordfeature.aggrega.ai/kind=secretnoenvyesOptional cache authentication credential. Every realization halts on an attachment, since none can enforce it: the memcached image the Kubernetes and Compose realizations run authenticates only through SASL over the binary protocol or an ASCII authentication file, which the catalog's Memcached clients do not use, and neither ElastiCache nor Memorystore for Memcached offers Memcached authentication. Unattached, the cache runs without authentication.
server_certificatefeature.aggrega.ai/kind=secretnofileyesOptional certificate the cache presents to its clients while infra.client_tls is true: a Secret holding tls.crt, the certificate followed by any intermediate certificates, and tls.key, its private key, the two keys a kubernetes.io/tls Secret holds. The certificate names every address a client dials: the published host, and its namespace-qualified forms where clients in other namespaces connect. Mounted as files, so attach a Feature that names an existing Secret, such as core/referenced-secret. Required by the Kubernetes realization while client_tls is true; a build halts on it attached while client_tls is false. ElastiCache presents a certificate AWS issues and Memorystore serves no TLS, so their realizations halt on any attachment here.

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