Use Case for ECS Cluster Underutilization Check
Quick Links
- Configure ECS Cluster Underutilization Check
- Use Case for ECS Cluster Underutilization Check
- Triage Guides by Violation Type
When to Use ECS Cluster Underutilization Check
This policy is used to identify Amazon Elastic Container Service (ECS) clusters that are underutilized according to average CPU and memory metrics. It is beneficial for cost optimization and efficiency.
Pros
- Cost Savings: Helps identify and reduce wasteful expenditure on under-utilized resources.
- Resource Optimization: Ensures that ECS clusters are sized appropriately for the workload.
Cons
- Potential Overhead: Additional monitoring and evaluation mechanisms.
How It Works
The policy evaluates the average CPU and memory utilization against user-defined thresholds. If utilization is below the set thresholds, it flags the cluster as underutilized.
Variables and Their Defaults
- cpuUtilizationThreshold: The CPU utilization threshold, default 20%.
- memoryUtilizationThreshold: The memory utilization threshold, default 20%.
- clusterAgeThreshold: The age in days before which the cluster is not evaluated, default 30 days.
Violation Types
- CPU_UNDERUTILIZATION: Indicates the cluster's CPU utilization is below the user-defined threshold.
- MEMORY_UNDERUTILIZATION: Indicates the cluster's memory utilization is below the user-defined threshold.