Ensure Redshift clusters are using the latest generation of nodes

AWS Cost Optimization

To ensure that your AWS account's Redshift clusters are utilizing the most cost-efficient and high-performing nodes, it is recommended to upgrade them to the latest generation nodes available. Upgrading from the previous generation of nodes such as ds1.xlarge or ds1.8xlarge to their latest generation equivalents (ds2.xlarge or ds2.8xlarge) can provide better computing capacity, faster CPUs, more RAM memory, and higher disk throughput using solid-state disks, all while maintaining the same cost. By upgrading to the latest generation of Redshift nodes, you can get the most out of your clusters at a lower cost.


Here are the remediation steps to ensure Redshift clusters are using the latest generation of nodes:

  1. Identify the Redshift clusters in your AWS account that are using nodes from the previous generation.
  2. Determine the latest generation of nodes that are compatible with your workload requirements.
  3. Create a plan to upgrade the Redshift clusters to the latest generation of nodes, taking into consideration any potential impact on your workload and any necessary downtime.
  4. Perform a backup of your Redshift clusters before initiating the node upgrade.
  5. Upgrade the nodes of the Redshift clusters to the latest generation, following the steps outlined in the Amazon Redshift documentation.
  6. Validate the new node configuration and test your workload to ensure that it is performing as expected.
  7. Monitor the Redshift clusters for any issues post-upgrade and address any that may arise.
  8. Repeat the process for any other Redshift clusters that are using nodes from the previous generation.
Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.