Amazon ElastiCache for Redis now supports auto scaling
Amazon ElastiCache for Redis now supports auto scaling to automatically adjust capacity to maintain steady, predictable performance at the lowest possible cost. You can automatically scale your cluster horizontally by adding or removing shards or replica nodes. ElastiCache for Redis uses AWS Application Auto Scaling to manage scaling and Amazon CloudWatch metrics to determine when it is time to scale up or down.
Amazon ElastiCache for Redis now supports auto scaling to automatically adjust capacity to maintain steady, predictable performance at the lowest possible cost. You can automatically scale your cluster horizontally by adding or removing shards or replica nodes. ElastiCache for Redis uses AWS Application Auto Scaling to manage scaling and Amazon CloudWatch metrics to determine when it is time to scale up or down.
ElastiCache for Redis supports target tracking and scheduled auto scaling policies. With target tracking, you define a target metric and ElastiCache for Redis adjusts resource capacity in response to live changes in resource utilization. The intention is to provide enough capacity to maintain utilization at the target value specified. For instance, when memory utilization rises, ElastiCache for Redis will add nodes to your cluster to increase memory capacity and reduce utilization back to the target level. This enables your cluster to adjust capacity automatically to maintain high performance. Conversely, when memory utilization drops below the target amount, ElastiCache for Redis will remove nodes from your cluster to reduce over-provisioning and lower costs. With scheduled scaling, you can set specific days and times for ElastiCache to scale your cluster to accommodate predictable workload capacity changes.
Amazon ElastiCache for Redis is available in US East (N. Virginia), EU (Ireland), Asia Pacific (Mumbai) and South America (Sao Paulo), and support for more regions is coming soon. Learn more about auto scaling in ElastiCache for Redis on the feature page and or ElastiCache documentation.