Skip to main content

Triage AWS EBS Low IOPS Volumes LOW_IOPS_VIOLATION

  1. Configure AWS EBS Low IOPS Volumes
  2. Use Case for AWS EBS Low IOPS Volumes
  3. Triage Guides by Violation Type
    1. Triage AWS EBS Low IOPS Volumes LOW_IOPS_VIOLATION

Triage Guide for LOW_IOPS_VIOLATION

Understand​

This alert indicates that the EBS volume type io1 or io2 has provisioned IOPS lower than 3000. Migrating these volumes to gp3 can provide cost savings while maintaining or even improving performance.

Validate​

  • Data Source: AWS EC2 API for describing volumes.
  • Manual Retrieval: You can describe the volume manually using the AWS CLI: sh aws ec2 describe-volumes --volume-ids <volume_id>
  • Schedule: This policy runs reactively when triggered by a specific resource.

Triage​

  • Impact: Leaving a low IOPS volume as is could result in higher costs without additional performance benefits.
  • Worsening: Costs will continue to be higher until the volume is migrated to a more efficient type.
  • Remediation Impact: Migrating volume types can cause service interruption if not handled properly.

Act​

  • Determine the feasibility of migrating the volume to gp3 based on your application’s requirements.
  • Follow AWS migration documentation to transition from io1 or io2 to gp3.

Reflect​

  • Accuracy Check: Ensure the alert criteria align with your business goals for cost and performance.
  • Adjustments: If this alert is too frequent or not useful, consider adjusting the IOPS threshold or disabling the policy.