Ensure that the number of Amazon Redshift cluster nodes provisioned in your AWS account has not reached the limit quota established by your organization for the Redshift workload deployed. By default, Cloud Conformity sets a threshold value of 5 for the maximum number of provisioned cluster nodes but you also have the capability to adjust this threshold based on your requirements, upon enabling this rule. Once you define your own threshold for the maximum number of Redshift cluster nodes that you need to run across all AWS regions, Cloud Conformity engine will start to continuously check your account for Redshift nodes and when the number of nodes reach the specified count (threshold) you will get notified via communication channels configured within your Cloud Conformity account. If the Redshift limit quota defined for your AWS account is reached, you can create an AWS support case to request limiting the number of provisioned Redshift nodes based on your requirements.
This rule can help you with the following compliance standards:
- APRA
- MAS
For further details on compliance standards supported by Conformity, see here.
This rule can help you work with the AWS Well-Architected Framework.
This rule resolution is part of the Conformity Security & Compliance tool for AWS.
Audit
To determine the number of Redshift cluster nodes provisioned within your AWS account, perform the following:
Remediation / Resolution
To raise an AWS support case to request limiting the number of provisioned Redshift cluster nodes in your AWS account based on your requirements, perform the following actions:
Note: Requesting a limit for the number of Redshift nodes per region using the AWS API via Command Line Interface (CLI) is not currently supported.References
- AWS Documentation
- Amazon RDS FAQs
- Amazon Redshift Clusters
- Limits in Amazon Redshift
- AWS Command Line Interface (CLI) Documentation
- redshift
- describe-clusters