⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 AWS → 📁 EC2
🛡️ AWS EBS Volume is underutilized🟢
- Contextual name: 🛡️ EBS Volume is underutilized🟢
- ID:
/ce/ca/aws/ec2/ebs-volume-underutilized
- Tags:
- Policy Type:
COMPLIANCE_POLICY
- Policy Categories:
COST
,PERFORMANCE
Logic
Description
Description
This policy identifies AWS EBS volumes of type
gp3
,io1
, andio2
that are underutilized based on their I/O operations over a 30-day period. A volume is considered underutilized if it is provisioned for high performance but exhibits low actual usage, indicating an opportunity for cost optimization.Criteria and Thresholds:
gp3
volumes:
- Volumes provisioned with IOPS above the free baseline of 3,000.
- Maximum theoretical operations per month for a 3,000 IOPS volume is 7,776,000,000 operations (calculated as 3,000 IOPS × 86,400 seconds/day × 30 days).
- The threshold of 1,944,000,000 operations corresponds to one-quarter of the maximum, serving as a marker for low utilization.
- Volumes below this threshold are considered good candidates to be downsized to the 3,000 IOPS baseline.
io1
andio2
volumes:
- Minimum provisioned IOPS for these volumes is 100 IOPS.
- Maximum theoretical operations per month for a 100 IOPS volume is 259,200,000 operations (100 IOPS × 86,400 seconds/day × 30 days).
... see more
Remediation
Remediation
Before downsizing, review historical performance metrics to ensure the volume can safely operate at a lower IOPS. Modifying volumes may cause temporary I/O latency.
Downsize the Volume
aws ec2 modify-volume \
--volume-id {{volume-id}} \
--volume-type {{volume-type}} \
--iops {{3000}}Verify Performance After Downsizing
Monitor CloudWatch metrics to ensure the downsized volume continues to meet performance requirements.
policy.yaml
Linked Framework Sections
Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
---|---|---|---|---|---|
💼 Cloudaware Framework → 💼 Resource Optimization | 23 | no data | |||
💼 Cloudaware Framework → 💼 Workload Efficiency | 24 | no data |