Connect to an external Redis database

LangSmith uses Redis to back our queuing/caching operations. By default, LangSmith Self-Hosted will use an internal Redis instance. However, you can configure LangSmith to use an external Redis instance. By configuring an external Redis instance, you can more easily manage backups, scaling, and other operational tasks for your Redis instance.

Requirements

A provisioned Redis instance that your LangSmith instance will have network access to. We recommend using a managed Redis service like:
Note: We only officially support Redis versions >= 5.
We support both Standalone and Redis Cluster. See the appropriate sections for deployment instructions.
By default, we recommend an instance with at least 2 vCPUs and 8GB of memory. However, the actual requirements will depend on your tracing workload. We recommend monitoring your Redis instance and scaling up as needed.

Standalone Redis

Connection String

You will need to assemble the connection string for your Redis instance. This connection string should include the following information:

Host
Database
Port
URL params

This will take the form of:

"redis://host:port/db?<url_params>"

An example connection string might look like:

"redis://langsmith-redis:6379/0"

Note: If your Standalone Redis requires authentication or TLS, include these directly in the connection URL:

Use rediss:// when TLS is enabled on your Redis server.
Provide the password in the connection string.

For example:

rediss://langsmith-redis:6380/0?password=foo

Configuration

With your connection string in hand, you can configure your LangSmith instance to use an external Redis instance. You can do this by modifying the values file for your LangSmith Helm Chart installation or the .env file for your Docker installation.

redis:
  external:
    enabled: true
    connectionUrl: "Your connection url"

# In your .env file
REDIS_DATABASE_URI="Your connection url"

You can also store the connection URL in an existing Kubernetes Secret and reference it in your Helm values.

redis:
  external:
    enabled: true
    # Name of an existing Secret that contains the connection URL
    existingSecretName: "my-redis-secret"
    # Key in the Secret that stores the connection URL (default shown)
    connectionUrlSecretKey: "connection_url"

apiVersion: v1
kind: Secret
metadata:
  name: my-redis-secret
type: Opaque
stringData:
  # Full connection URL, e.g., using TLS with password
  connection_url: "rediss://langsmith-redis:6380/0?password=foo"

Once configured, you should be able to reinstall your LangSmith instance. If everything is configured correctly, your LangSmith instance should now be using your external Redis instance.

Redis Cluster

As of LangSmith helm version 0.12.25, we officially support Redis Cluster.

Host Names

When using Redis Cluster, provide a list of node hostnames and ports. Each node URI must be in the form:

redis://hostname:port

For example:

redis://redis-node-0:6379
redis://redis-node-1:6379
redis://redis-node-2:6379

Do not include a password in these URIs, and do not use rediss here. For Redis Cluster:

Provide the password separately via redis.external.cluster.password or through a Secret using passwordSecretKey.
Enable TLS separately with redis.external.cluster.tlsEnabled: true.

Configuration

When connecting to an external Redis Cluster, configure the Helm values under redis.external.cluster. You can either:

Provide node URIs and (optionally) a password directly in values.yaml.
Or reference an existing Kubernetes Secret containing node URIs and password.

redis:
  external:
    enabled: true
    cluster:
      enabled: true
      # List of cluster node URIs. Format: redis://host:port
      nodeUris:
        - "redis://redis-node-0:6379"
        - "redis://redis-node-1:6379"
        - "redis://redis-node-2:6379"
      # Optional. If your cluster requires auth, set a password or use a Secret (recommended).
      password: "your_redis_password"
      # Enable if your cluster uses TLS.
      tlsEnabled: true

redis:
  external:
    enabled: true
    # Name of an existing Secret that contains cluster connection details
    existingSecretName: "my-redis-cluster-secret"
    cluster:
      enabled: true
      # Keys in the Secret. Defaults shown here; override if your Secret uses different keys.
      nodeUrisSecretKey: "redis_cluster_node_uris"
      passwordSecretKey: "redis_cluster_password"
      tlsEnabled: true

If using an existing Secret, it should contain:

apiVersion: v1
kind: Secret
metadata:
  name: my-redis-cluster-secret
type: Opaque
stringData:
  # JSON array of node URIs (as a string)
  redis_cluster_node_uris: '["redis://redis-node-0:6379","redis://redis-node-1:6379","redis://redis-node-2:6379"]'
  # Optional if your cluster requires a password
  redis_cluster_password: "your_redis_password"

TLS with Redis

Use this section to configure TLS for Redis connections. For mounting internal/public CAs so LangSmith trusts your Redis server certificate, see Configure custom TLS certificates.

Server TLS (one-way)

To validate the Redis server certificate:

Provide a CA bundle using config.customCa.secretName and config.customCa.secretKey.
For Standalone Redis, use rediss:// in the connection URL.
For Redis Cluster, set redis.external.cluster.tlsEnabled: true.

Mount a custom CA only when your Redis server uses an internal or private CA. Publicly trusted CAs do not require this configuration.

config:
  customCa:
    secretName: "langsmith-custom-ca"  # Secret containing your CA bundle
    secretKey: "ca.crt"    # Key in the Secret with the CA bundle
redis:
  external:
    enabled: true
    # Use rediss:// and include password if required by your server
    connectionUrl: "rediss://host:6380/0?password=<PASSWORD>"

config:
  customCa:
    secretName: "langsmith-custom-ca"  # Secret containing your CA bundle
    secretKey: "ca.crt"    # Key in the Secret with the CA bundle
redis:
  external:
    enabled: true
    cluster:
      enabled: true
      tlsEnabled: true
      nodeUris:
        - "redis://redis-node-0:6379"
        - "redis://redis-node-1:6379"
        - "redis://redis-node-2:6379"
      password: "<PASSWORD>"

apiVersion: v1
kind: Secret
metadata:
  name: langsmith-custom-ca
type: Opaque
stringData:
  ca.crt: |
    -----BEGIN CERTIFICATE-----
    <ROOT_OR_INTERMEDIATE_CA_CERT_CHAIN>
    -----END CERTIFICATE-----

Mutual TLS with Client Auth (mTLS)

As of LangSmith helm chart version 0.12.28, we support mTLS for Redis clients. For server-side authentication in mTLS, use the Server TLS steps above (custom CA) in addition to the client certificate configuration below. If your Redis server requires client certificate authentication:

Provide a Secret with your client certificate and key.
Reference it via redis.external.clientCert.secretName and specify the keys with certSecretKey and keySecretKey.
For Standalone Redis, keep using rediss:// in the connection URL.
For Redis Cluster, set redis.external.cluster.tlsEnabled: true.

redis:
  external:
    enabled: true
    clientCert:
      secretName: "redis-mtls-secret"
      certSecretKey: "tls.crt"
      keySecretKey: "tls.key"
    # Standalone example:
    # connectionUrl: "rediss://host:6380/0?password=<PASSWORD>"
    # Or, for Cluster:
    cluster:
      enabled: true
      tlsEnabled: true
      nodeUris:
        - "redis://redis-node-0:6379"
        - "redis://redis-node-1:6379"
        - "redis://redis-node-2:6379"
      password: "<PASSWORD>"

apiVersion: v1
kind: Secret
metadata:
  name: redis-mtls-secret
type: Opaque
stringData:
  tls.crt: |
    -----BEGIN CERTIFICATE-----
    <CLIENT_CERT>
    -----END CERTIFICATE-----
  tls.key: |
    -----BEGIN PRIVATE KEY-----
    <CLIENT_KEY>
    -----END PRIVATE KEY-----

Pod security context for certificate volumes

The certificate volumes mounted for mTLS are protected by file access restrictions. To ensure all LangSmith pods can read the certificate files, you must set fsGroup: 1000 in the pod security context. You can configure this in one of two ways: Option 1: Use commonPodSecurityContext Set the fsGroup at the top level to apply it to all pods:

commonPodSecurityContext:
  fsGroup: 1000

Option 2: Add to individual pod security contexts If you need more granular control, add the fsGroup to each pod’s security context individually. See the mtls configuration example for a complete reference.

Edit the source of this page on GitHub.

Connect these docs programmatically to Claude, VSCode, and more via MCP for real-time answers.

Overview

Self-hosted cloud architecture

Hybrid

Self-hosted

Connect to an external Redis database

Requirements

Standalone Redis

Connection String

Configuration

Redis Cluster

Host Names

Configuration

TLS with Redis

Server TLS (one-way)

Mutual TLS with Client Auth (mTLS)

Pod security context for certificate volumes

​Requirements

​Standalone Redis

​Connection String

​Configuration

​Redis Cluster

​Host Names

​Configuration

​TLS with Redis

​Server TLS (one-way)

​Mutual TLS with Client Auth (mTLS)

​Pod security context for certificate volumes

Requirements

Standalone Redis

Connection String

Configuration

Redis Cluster

Host Names

Configuration

TLS with Redis

Server TLS (one-way)

Mutual TLS with Client Auth (mTLS)

Pod security context for certificate volumes