Benchmark: Redshift Checks
Thrifty Redshift Benchmark
Thrifty developers check whether their long-running Redshift clusters are associated with reserved nodes.
Variables
Variable | Description | Default |
---|---|---|
redshift_cluster_avg_cpu_utilization_high | The average CPU utilization required for clusters to be considered frequently used. This value should be higher than redshift_cluster_avg_cpu_utilization_low . | 35% |
redshift_cluster_avg_cpu_utilization_low | The average CPU utilization required for clusters to be considered infrequently used. This value should be lower than redshift_cluster_avg_cpu_utilization_high . | 20% |
redshift_running_cluster_age_max_days | The maximum number of days clusters are allowed to run. | 90 days |
redshift_running_cluster_age_warning_days | The number of days clusters can be running before sending a warning. | 30 days |
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-thrifty
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select Redshift Checks.
Run this benchmark in your terminal:
powerpipe benchmark run aws_thrifty.benchmark.redshift
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_thrifty.benchmark.redshift --share
Controls
- Redshift cluster with low CPU utilization should be reviewed
- Long running Redshift clusters should have reserved nodes purchased for them
- Redshift cluster paused resume should be enabled