Providers

Redis Cloud

Redis Ltd. managed Redis — Configuration tab endpoints, Connect wizard, rediss://, dynamic vs static endpoints.

Redis Cloud is Redis Ltd.'s first-party managed service — RESP over TCP/TLS, no separate REST layer. drivers.store.kv stays redis.

The one rule

Use rediss:// (double s) with the endpoint from Configuration or the Connect wizard. Prefer dynamic endpoints when both are offered.

Find credentials (current console)

  1. Open Redis Cloud → your database.
  2. Open the Configuration tab:
    • Essentials: endpoint under Access
    • Pro: endpoint under General (expand Dynamic endpoints if shown)
  3. Credentials:
    • Essentials: Default user → Configure → eye icon for password (default)
    • Pro: Security section on Configuration → eye icon for default user password
  4. Or click Connect → connection wizard → copy the ready-made client / redis-cli snippet (fills host, port, user, password).
process env
REDIS_URL=rediss://default:PASSWORD@redis-12345.c1.region.cloud.redislabs.com:12345
# or dynamic: …@horse-battery-staple-12345.db.redis.io:…

Port is a per-database high port, not always 6379 — copy it from the panel.

Production guidance

TopicGuidance
TLSPublic endpoints expect TLS → rediss://
Endpoint typeDynamic (*.db.redis.io) can be redirected later; static redis-….c… cannot
PrivatePro private endpoint needs VPC peering / PrivateLink / PSC first
ModulesRediSearch / RedisJSON optional — unused by oke's KV driver
PortPer-database high port from Configuration — never assume 6379

Essentials vs Pro panels differ (Access vs General), but Connect always opens the wizard with a filled client snippet — prefer that when the Configuration layout feels unfamiliar after a UI refresh.

Real gotcha — dynamic vs static

Apps hard-coded to a static redis-….c… host cannot follow a later “redirect dynamic endpoint” migration. Copy the dynamic endpoint from Configuration when both exist so you can repoint without code changes.

Troubleshooting

Learn more

Next

On this page