Identify any Amazon ElastiCache cluster nodes that appear to be idle and remove them from your account to help lower the cost of your monthly AWS bill. By default, an AWS ElastiCache node is considered 'idle' when meets the following criteria:
The average CPU Utilization has been less than 2% for the last 7 days.
- The AWS CloudWatch metrics used to detect idle ElastiCache clusters are:
CPUUtilization (host-level metric) - the percentage of CPU resources used by ElastiCache cache nodes (Units: Percentage).
Idle Amazon ElastiCache cache cluster nodes represent a good candidate to reduce your monthly AWS costs and avoid accumulating unnecessary usage charges.
Case A: To determine if you have any idle ElastiCache Memcached cluster nodes within your AWS account, perform the following:
Case B: To determine if you have any idle ElastiCache Redis cluster nodes within your AWS account, perform the following:
Option 1: Delete any AWS ElastiCache clusters that are currently running in idle mode. To remove the idle cache clusters, perform the following actions:
Option 2: Disable the rule check. If the selected idle Amazon ElastiCache cluster is needed (its role within your application stack/environment is important), you may want turn off the conformity rule check for the specified ElastiCache cluster from the Cloud Conformity console