Identify any Amazon Redshift clusters that appear to be idle and delete them to help lower the cost of your monthly AWS bill. By default, a Redshift cluster is considered 'idle' when meets the following criteria (to declare the cluster 'idle' both conditions must be true):
- The average number of database connections has been less than 1 for the last 7 days.
- The total number of ReadIOPS and WriteIOPS recorded per day for the last 7 days has been less than 20 on average.
The AWS CloudWatch metrics used to detect idle Redshift clusters are:
- DatabaseConnections - the number of database connections made to a Redshift cluster (Units: Count).
- ReadIOPS and WriteIOPS - the average number of disk I/O (Input/Output) operations per second (Units: Count/Second).
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS
Idle Redshift clusters represent a good candidate for reducing your monthly AWS costs and avoid accumulating unnecessary usage charges.
Note 1: Backing up your Redshift clusters before termination is highly recommended because once these clusters are deleted, all their automated backups (snapshots) will be removed as well.
Note 2: Knowing the role and the owner of an AWS Redshift cluster before you take the decision to remove it from your account is very important. For this rule Cloud Conformity assumes that your Redshift clusters are tagged with 'Role' and 'Owner' tags which provide visibility into their usage profile and help you decide whether it's safe or not to terminate these resources.
Note 3: You can change the default threshold for this rule on the Cloud Conformity console and set your own values for the number of database connections, the total number of ReadIOPS and WriteIOPS for each condition in order to configure the clusters idleness.
Note 4: If the Redshift cluster selected for the checkup is needed within your AWS environment, you can suppress (disable) the conformity rule check for the cluster from the Cloud Conformity console.
To identify any idle Redshift clusters currently provisioned within your AWS account, perform the following:
Remediation / Resolution
Option 1: terminate the idle clusters. To terminate (delete) any AWS Redshift clusters that are currently running in idle mode, perform the following commands:
Option 2: disable the rule check. If the selected idle Redshift cluster is needed (its role within your environment/application stack is important), you should turn off the conformity rule check for the cluster from the Cloud Conformity console.
- AWS Documentation
- Trusted Advisor Best Practices (Checks)
- Amazon Redshift Clusters
- Summary of Amazon Redshift Performance Data
- Managing Clusters Using the Console
Unlock the Remediation Steps
Gain free unlimited access
to our full Knowledge Base
Over 750 rules & best practices
Get started for FREE
You are auditing:
Idle Redshift Cluster
Risk level: High