---
title: Using Redis Sentinel
url: https://www.tines.com/docs/self-hosted/configuring-tines/using-redis-sentinel/
updated: 2026-03-30T18:03:55+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt) › [Self-Hosted](https://www.tines.com/llm/docs/self-hosted.md) › [Configuring Tines](https://www.tines.com/llm/docs/self-hosted/configuring-tines.md)*

# Using Redis Sentinel

*[View on tines.com](https://www.tines.com/docs/self-hosted/configuring-tines/using-redis-sentinel/)*

Redis Sentinel handles automatic failover of Redis masters and service discovery. Tines can now use Redis Sentinel. It is currently available in the `v13.3.4` version (experimental). 

**Please note**, we only recommend usage of Redis Sentinel when usage of services like AWS Elasticache or similar isn't an option.

In order for your Tines installation to work with Redis Sentinel, you will need to setup the following environment variables:

**Required**

- `REDIS_SENTINEL_ENDPOINTS`: A comma separated list of sentinel endpoints with port:
  
  - Example: `export REDIS_SENTINEL_ENDPOINTS="redis://redis-sentinel:26379,redis://redis-sentinel:26380"`
- `REDIS_SENTINEL_MASTER_NAME` 
  
  - Default `master`

**Optional**

For TLS and authentication purposes:

- `REDIS_SENTINEL_PASSWORD`
- `REDIS_SENTINEL_USE_SSL`
  
  - This should be set to true in order to use TLS/SSL based connection with Redis sentinels.
  - Example: `export REDIS_SENTINEL_USE_SSL=true`
- `REDIS_SENTINEL_CA_FILE_PATH`
  
  - Location of the respective file (only used if `REDIS_SENTINEL_USE_SSL` is true)
- `REDIS_SENTINEL_CERT_FILE_PATH`
  
  - Location of the respective file (only used if `REDIS_SENTINEL_USE_SSL` is true)
- `REDIS_SENTINEL_KEY_FILE` 
  
  - Location of the respective file (only used if `REDIS_SENTINEL_USE_SSL` is true)



**Note** : Not providing `REDIS_SENTINEL_ENDPOINTS` will default the application to use `REDIS_URL` as the base URL for connecting to standard Redis.