Scaling ElastiCache (Redis OSS) self-designed clusters

The amount of data your application needs to process is seldom static. It increases and decreases as your business grows or experiences normal fluctuations in demand. If you self-manage your cache, you need to provision sufficient hardware for your demand peaks, which can be expensive. By using Amazon ElastiCache you can scale to meet current demand, paying only for what you use. ElastiCache enables you to scale your cache to match demand.

Note

If a Redis OSS cluster is replicated across one or more Regions, then those Regions are scaled in order. When scaling up, secondary Regions are scaled first and then the primary Region. When scaling down, the primary Region is first and then any secondary Regions follow.

When updating the engine version, the order is secondary Region and then primary Region.

The following helps you find the correct topic for the scaling actions that you want to perform.

Scaling Redis OSS clusters
Action	Redis OSS (cluster mode disabled)	Redis OSS (cluster mode enabled)
Scaling in	Removing nodes from an ElastiCache cluster	Scaling clusters in Redis OSS (Cluster Mode Enabled)
Scaling out	Adding nodes to a cluster	Online resharding for Redis OSS (cluster mode enabled)
Changing node types	To a larger node type: Scaling up single-node Redis OSS clusters Scaling up Redis OSS clusters with replicas To a smaller node type: Scaling down single-node Redis OSS clusters Scaling down Redis OSS clusters with replicas	Online vertical scaling by modifying node type
Changing the number of node groups	Not supported for Redis OSS (cluster mode disabled) clusters	Scaling clusters in Redis OSS (Cluster Mode Enabled)

Topics

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Scaling ElastiCache (Redis OSS)

Scaling clusters for Redis OSS (Cluster Mode Disabled)