Redis
Redis OSS, Redis Cloud, Amazon ElastiCache, Azure Cache for Redis.
Access mode: Read-only
Trino connector. Queryable via Flume’s Lakehouse. This system can be accessed both through its native protocol (for metadata introspection) and via Trino federation (for data profiling and cross-system analytical queries).
Required information
| Field | Details |
|---|---|
| Host / IP | Redis server endpoint. Cluster: provide the configuration endpoint. Cloud services: managed endpoint URL. |
| Port | Default 6379. TLS: 6380 (Azure) or same port with TLS enabled. |
| Database index | Redis database number (0 to 15). Default 0. |
| Key patterns | Key naming patterns to scope access (e.g., user:*, session:*). Redis doesn’t have tables; keys are the schema. |
| Data structure types | What Redis data structures are in use: strings, hashes, lists, sets, sorted sets, streams. Determines how Trino maps them. |
| Authentication | AUTH password (Redis 5-), username + password (Redis 6+ ACL system), or IAM (ElastiCache). |
| SSL/TLS | Required for most managed services. |
Network considerations
Redis Cloud: TLS over default port. IP allowlisting or VPC peering.
ElastiCache: VPC-based. Requires VPC peering or PrivateLink. Not publicly accessible by default.
Azure Cache: TLS on port 6380. VNet injection or Private Endpoint.
Self-managed: VPN or direct access. Default binds to 127.0.0.1, so it must be configured for remote access.
Redis Cluster: Flume must be able to reach all nodes (driver follows MOVED/ASK redirections). Firewall must allow the full port range.
Trino access: Flume’s Lakehouse queries Redis via the Trino Redis connector, which maps key patterns to table schemas.
Credential and auth management
Redis 6+ ACL system (preferred): Create a dedicated user with +@read category and restricted key patterns (~user:*).
Legacy AUTH: Single password for the entire instance. No user-level granularity.
ElastiCache IAM: Redis 7+ on ElastiCache supports IAM auth. Flume authenticates via IAM role.
Azure AD (Entra ID): Azure Cache for Redis supports Azure AD auth for data plane operations.
No session management: Redis connections are persistent TCP. Connection pooling handled by Flume.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Network reachability | redis-cli -h <host> -p <port> ping | Returns PONG |
| Authentication | redis-cli AUTH <user> <pass> then INFO server | Returns server info |
| Key access | SCAN 0 MATCH <pattern> COUNT 10 | Returns matching keys |
| Read test | GET <key> or HGETALL <key> depending on type | Returns value |
| ACL check | ACL WHOAMI | Returns authenticated user |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.