Control: ECS clusters with low CPU utilization should be reviewed
Description
Resize or eliminate under utilized clusters.
Usage
Run the control in your terminal:
powerpipe control run aws_thrifty.control.ecs_cluster_low_utilization
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run aws_thrifty.control.ecs_cluster_low_utilization --share
Steampipe Tables
Params
Args | Name | Default | Description | Variable |
---|---|---|---|---|
$1 | ecs_cluster_avg_cpu_utilization_low |
| The average CPU utilization required for clusters to be considered infrequently used. This value should be lower than ecs_cluster_avg_cpu_utilization_high. | |
$2 | ecs_cluster_avg_cpu_utilization_high |
| The average CPU utilization required for clusters to be considered frequently used. This value should be higher than ecs_cluster_avg_cpu_utilization_low. |
SQL
with ecs_cluster_utilization as ( select cluster_name, round(cast(sum(maximum)/count(maximum) as numeric), 1) as avg_max, count(maximum) days from aws_ecs_cluster_metric_cpu_utilization_daily where date_part('day', now() - timestamp) <= 30 group by cluster_name)select i.cluster_name as resource, case when avg_max is null then 'error' when avg_max < $1 then 'alarm' when avg_max < $2 then 'info' else 'ok' end as status, case when avg_max is null then 'CloudWatch metrics not available for ' || title || '.' else title || ' is averaging ' || avg_max || '% max utilization over the last ' || days || ' days.' end as reason , region, account_idfrom aws_ecs_cluster as i left join ecs_cluster_utilization as u on u.cluster_name = i.cluster_name;