Can I enable cluster-enabled on an existing ElastiCache Redis replication group that was created without it?

No, cluster mode (sharding across multiple shards) is a create-time architectural decision for the replication group, it cannot be toggled via a parameter group update on an existing cluster. Moving from cluster mode disabled to enabled requires creating a new cluster-mode-enabled replication group and migrating data into it, not a parameter change.

What's the actual effect of setting maxmemory-policy to allkeys-lru versus volatile-lru?

allkeys-lru evicts the least-recently-used key from the entire keyspace when memory fills, regardless of whether that key has a TTL set, appropriate for a pure cache where every key is disposable. volatile-lru only evicts among keys that have an expiration (TTL) set, leaving non-TTL keys untouched even under memory pressure, which matters if you're storing some genuinely persistent data alongside cacheable data in the same Redis instance and can't afford to lose the non-TTL keys.

Does enabling activedefrag have a performance cost?

Yes, active defragmentation runs as a background process consuming some CPU to scan and compact memory, the active-defrag-threshold-lower/upper values control when it kicks in (only once fragmentation exceeds a threshold) specifically to balance the CPU cost of defragmenting against the memory waste of not doing so. It's most valuable for workloads with high key churn causing real fragmentation, and less valuable (pure overhead) for a workload with mostly stable, long-lived keys.

AWS ElastiCache Parameter Group Builder

StorageAWS

Build ElastiCache parameter group configurations for Redis and Memcached with optimized memory, eviction, and cluster settings.

Amazon ElastiCache Configuration

Build ElastiCache parameter group configurations for Redis and Memcached with optimized memory, eviction, and cluster settings.

Required Fields

CacheParameterGroupNameCacheParameterGroupFamilyDescriptionParameters

Generated Output

Output will appear here...

About This Tool

Build a Redis-family ElastiCache parameter group tuning eviction (maxmemory-policy), active defragmentation thresholds, lazy-free background deletion, and cluster mode. cluster-enabled: yes is a create-time-only decision for a Redis cluster, it can't be toggled on an existing non-cluster-mode replication group after the fact, migrating between cluster mode disabled and enabled requires creating a new cluster and migrating data, not a parameter update, which makes this single parameter one of the highest-stakes choices in the whole group.

When to Use This Tool

•Setting maxmemory-policy to allkeys-lru for a pure cache use case (evict any key when memory fills, not just keys with a TTL set) versus volatile-lru for a mixed cache-plus-persistent-data use case where non-TTL keys must never be evicted.
•Enabling activedefrag with tuned active-defrag-threshold-lower/upper values for a workload with high key churn (frequent small object updates) that causes Redis memory fragmentation over time, reclaiming that wasted memory without a full restart.
•Setting lazyfree-lazy-eviction, lazyfree-lazy-expire, and lazyfree-lazy-server-del all to yes so large key deletions happen on a background thread instead of blocking the single main Redis thread, avoiding latency spikes when a big key or many keys are evicted/expired at once.
•Setting notify-keyspace-events to Ex specifically to enable keyspace notifications for expired-key events, a common pattern for building an application-level cache-invalidation or session-expiry hook that reacts to Redis TTL expirations.

Pro Tips

TIP

cluster-enabled is the one parameter in this group you truly cannot change later without a migration, get the cluster-mode decision right at initial design time based on expected dataset size and whether you need horizontal sharding, not as an afterthought.

TIP

lazyfree-lazy-* settings are close to a free win for most workloads with any large keys or bulk deletions, enabling them moves expensive delete/expire work off the single main thread, reducing tail latency, with minimal downside for most use cases.

TIP

notify-keyspace-events adds real overhead proportional to how many event types you subscribe to, scope it to exactly the event types your application actually consumes (like Ex for expired events only) rather than enabling broad notification classes you don't use.

How It Works Under the Hood

The builder validates that CacheParameterGroupName, CacheParameterGroupFamily, Description, and Parameters all resolve before accepting the JSON as a valid CreateCacheParameterGroup request, the fields ElastiCache needs to create a named parameter group tied to a specific engine family; it can't verify that every listed parameter name and value is actually valid for the specified family, that's checked only against the live ElastiCache API, which rejects unrecognized or out-of-range parameters.

Frequently Asked Questions

Can I enable cluster-enabled on an existing ElastiCache Redis replication group that was created without it?: No, cluster mode (sharding across multiple shards) is a create-time architectural decision for the replication group, it cannot be toggled via a parameter group update on an existing cluster. Moving from cluster mode disabled to enabled requires creating a new cluster-mode-enabled replication group and migrating data into it, not a parameter change.
What's the actual effect of setting maxmemory-policy to allkeys-lru versus volatile-lru?: allkeys-lru evicts the least-recently-used key from the entire keyspace when memory fills, regardless of whether that key has a TTL set, appropriate for a pure cache where every key is disposable. volatile-lru only evicts among keys that have an expiration (TTL) set, leaving non-TTL keys untouched even under memory pressure, which matters if you're storing some genuinely persistent data alongside cacheable data in the same Redis instance and can't afford to lose the non-TTL keys.
Does enabling activedefrag have a performance cost?: Yes, active defragmentation runs as a background process consuming some CPU to scan and compact memory, the active-defrag-threshold-lower/upper values control when it kicks in (only once fragmentation exceeds a threshold) specifically to balance the CPU cost of defragmenting against the memory waste of not doing so. It's most valuable for workloads with high key churn causing real fragmentation, and less valuable (pure overhead) for a workload with mostly stable, long-lived keys.

Related Learning Guides

S3 Storage Classes Explained24 min read
DynamoDB Data Modeling28 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.

AWS ElastiCache Parameter Group Builder

StorageAWS

Build ElastiCache parameter group configurations for Redis and Memcached with optimized memory, eviction, and cluster settings.

Amazon ElastiCache Configuration

Build ElastiCache parameter group configurations for Redis and Memcached with optimized memory, eviction, and cluster settings.

Required Fields

CacheParameterGroupNameCacheParameterGroupFamilyDescriptionParameters

Generated Output

Output will appear here...

About This Tool

When to Use This Tool

•Setting maxmemory-policy to allkeys-lru for a pure cache use case (evict any key when memory fills, not just keys with a TTL set) versus volatile-lru for a mixed cache-plus-persistent-data use case where non-TTL keys must never be evicted.
•Enabling activedefrag with tuned active-defrag-threshold-lower/upper values for a workload with high key churn (frequent small object updates) that causes Redis memory fragmentation over time, reclaiming that wasted memory without a full restart.
•Setting lazyfree-lazy-eviction, lazyfree-lazy-expire, and lazyfree-lazy-server-del all to yes so large key deletions happen on a background thread instead of blocking the single main Redis thread, avoiding latency spikes when a big key or many keys are evicted/expired at once.
•Setting notify-keyspace-events to Ex specifically to enable keyspace notifications for expired-key events, a common pattern for building an application-level cache-invalidation or session-expiry hook that reacts to Redis TTL expirations.

Pro Tips

TIP

How It Works Under the Hood

Frequently Asked Questions

Can I enable cluster-enabled on an existing ElastiCache Redis replication group that was created without it?: No, cluster mode (sharding across multiple shards) is a create-time architectural decision for the replication group, it cannot be toggled via a parameter group update on an existing cluster. Moving from cluster mode disabled to enabled requires creating a new cluster-mode-enabled replication group and migrating data into it, not a parameter change.
What's the actual effect of setting maxmemory-policy to allkeys-lru versus volatile-lru?: allkeys-lru evicts the least-recently-used key from the entire keyspace when memory fills, regardless of whether that key has a TTL set, appropriate for a pure cache where every key is disposable. volatile-lru only evicts among keys that have an expiration (TTL) set, leaving non-TTL keys untouched even under memory pressure, which matters if you're storing some genuinely persistent data alongside cacheable data in the same Redis instance and can't afford to lose the non-TTL keys.
Does enabling activedefrag have a performance cost?: Yes, active defragmentation runs as a background process consuming some CPU to scan and compact memory, the active-defrag-threshold-lower/upper values control when it kicks in (only once fragmentation exceeds a threshold) specifically to balance the CPU cost of defragmenting against the memory waste of not doing so. It's most valuable for workloads with high key churn causing real fragmentation, and less valuable (pure overhead) for a workload with mostly stable, long-lived keys.

Related Learning Guides

S3 Storage Classes Explained24 min read
DynamoDB Data Modeling28 min read

Was this tool helpful?