Managed Redis

High-performance managed Redis for caching, session storage, and real-time applications

Fully managed Redis service with high availability, automatic failover, and enterprise-grade performance for caching and real-time data processing.

Overview#

• High Performance: Sub-millisecond latency
• High Availability: Automatic failover with Redis Sentinel
• Persistence: RDB and AOF backup options
• Scalability: Clustering for horizontal scaling
• Security: Encryption, ACLs, and network isolation

Key Features#

Performance#

• In-memory data storage
• Sub-millisecond response times
• Pipelining support
• Lua scripting
• Pub/Sub messaging

High Availability#

• Redis Sentinel for failover
• Multi-AZ deployment
• Automatic replica promotion
• Read replicas
• 99.99% uptime SLA

Data Persistence#

• RDB snapshots
• AOF (Append-Only File)
• Configurable persistence
• Backup scheduling
• Point-in-time recovery

Scalability#

• Redis Cluster support
• Horizontal sharding
• Up to 500 nodes
• Automatic rebalancing
• Connection pooling

Security#

• TLS encryption
• ACL authentication
• VPC isolation
• Password protection
• Audit logging

Supported Versions#

• Redis 7.2
• Redis 7.0
• Redis 6.2
• Redis 6.0

Use Cases#

Caching#

• Application cache
• Database query cache
• API response cache
• Session cache
• CDN cache

Session Storage#

• User sessions
• Shopping carts
• Authentication tokens
• Temporary data
• Rate limiting

Real-Time Analytics#

• Leaderboards
• Counters
• Real-time metrics
• Activity feeds
• Live dashboards

Message Queues#

• Job queues
• Task scheduling
• Event streaming
• Pub/Sub messaging
• Real-time notifications

Getting Started#

Connection#

1
redis-cli -h redis.company.com -p 6379 -a your_password --tls

Application Integration#

1
import redis
2
3
r = redis.Redis(
4
    host='redis.company.com',
5
    port=6379,
6
    password='your_password',
7
    ssl=True,
8
    decode_responses=True
9
)
10
11
# Set and get values
12
r.set('key', 'value')
13
value = r.get('key')

Node.js Example#

1
const redis = require('redis');
2
3
const client = redis.createClient({
4
  socket: {
5
    host: 'redis.company.com',
6
    port: 6379,
7
    tls: true
8
  },
9
  password: 'your_password'
10
});
11
12
await client.connect();
13
await client.set('key', 'value');
14
const value = await client.get('key');

Data Structures#

Supported Types#

• Strings: Simple key-value pairs
• Hashes: Field-value maps
• Lists: Ordered collections
• Sets: Unique unordered collections
• Sorted Sets: Ordered by score
• Streams: Log data structures
• Bitmaps: Bit-level operations
• HyperLogLog: Cardinality estimation
• Geospatial: Location data

Management Features#

Automated Operations#

• Automatic failover
• Maintenance windows
• Version upgrades
• Health monitoring
• Performance alerts

Monitoring#

• Memory usage
• CPU utilization
• Network throughput
• Command statistics
• Slow log analysis

Scaling#

• Vertical scaling (memory)
• Horizontal scaling (cluster)
• Read replica addition
• Connection limit tuning

Configuration Options#

Eviction Policies#

• noeviction
• allkeys-lru
• volatile-lru
• allkeys-lfu
• volatile-lfu
• allkeys-random
• volatile-random
• volatile-ttl

Persistence Options#

• RDB snapshots
• AOF logging
• Hybrid RDB+AOF
• No persistence (cache-only)

Pricing#

Based on:

• Instance size (memory)
• Number of nodes
• Data transfer
• Backup storage
• Support level

Support#

• 24/7 technical support
• Performance optimization
• Architecture consultation
• Migration assistance

Frequently Asked Questions#

What's the maximum memory size available? Single-node instances support up to 64GB of memory. For larger datasets, use Redis Cluster which supports up to 500 nodes and petabytes of data.

How do I choose an eviction policy? allkeys-lru is best for caching (evicts least recently used keys). volatile-ttl evicts keys with the shortest TTL. noeviction returns errors when memory is full—use for critical data that shouldn't be evicted.

Is data persisted to disk? Yes, we support RDB snapshots and AOF (Append-Only File) persistence. For pure caching, you can disable persistence for better performance. Data is always replicated for high availability.

Can I use Redis for message queues? Yes, Redis Streams provide a robust message queue with consumer groups. For simpler use cases, Redis Lists with LPUSH/BRPOP work well. For pub/sub messaging, use Redis Pub/Sub channels.

What's the latency I can expect? Sub-millisecond latency for most operations when the client is in the same region. Network latency dominates—deploy Redis close to your application servers.

Related Resources#

• Managed PostgreSQL — Primary database to cache
• Managed MySQL — Alternative database option
• SRE as a Service — Monitoring and incident response