Benchmark: ECS Checks
Thrifty ECS Benchmark
Thrifty developers eliminate their underutilized ECS clusters and ECS services without an autoscaling policy. This benchmark focuses on finding ECS clusters that have low utilization and an ECS service without an autoscaling policy.
Variables
| Variable | Description | Default |
|---|---|---|
| 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. | 35% |
| 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. | 20% |
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-thriftyStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select ECS Checks.
Run this benchmark in your terminal:
powerpipe benchmark run aws_thrifty.benchmark.ecsSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_thrifty.benchmark.ecs --shareControls
- ECS cluster container instances without graviton processor should be reviewed
- ECS clusters with low CPU utilization should be reviewed
- ECS service should use autoscaling policy