Skip to main content

Use Case for AWS EBS Low IOPS Volumes

  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

AWS EBS Low IOPS Volumes

Why Use This Policy?​

This policy aids in identifying AWS Elastic Block Store (EBS) volumes that are provisioned with IOPS lower than the base performance offered by General Purpose SSD (gp3) volumes. By migrating these volumes to gp3, significant cost savings can be achieved without sacrificing performance.

Pros:​

  • Cost Savings: Transitioning to gp3 volumes can reduce storage costs.
  • Efficiency: Ensures efficient use of IOPS where needed most.

Cons:​

  • Initial Setup: Requires migration configuration which could involve manual effort.
  • Compatibility: Ensure the application can handle the changes during migration.

How the Policy Works​

Variables​

  • thresholdIops: The IOPS threshold to identify low-performing volumes. Default is 3000.

Functionality​

  • The policy scans a specified EBS volume to check if the volume type is either io1 or io2 and if the IOPS is less than or equal to 3000.
  • If the conditions are matched, a violation is generated indicating a low IOPS volume.

Violation Types​

  • LOW_IOPS_VIOLATION: Raised when a provisioned IOPS volume (io1 or io2) has IOPS less than or equal to 3000.