Skip to main content

Triage AWS EBS io1 Volume IS_IO1_VOLUME

  1. Configure AWS EBS io1 Volume
  2. Use Case for AWS EBS io1 Volume
  3. Triage Guides by Violation Type
    1. Triage AWS EBS io1 Volume IS_IO1_VOLUME

Triage Guide: IS_IO1_VOLUME Violation

Understand​

Why should I care about fixing this issue?

EBS volumes using the io1 type are outdated. Upgrading to io2 volumes provides better reliability and potentially cost savings, particularly above 32,000 IOPS.

Validate​

How am I sure that this alert is true and accurate?

  • Data Source: The policy uses AWS SDK's DescribeVolumesCommand to fetch volume information.
  • Manual Retrieval: You can manually verify by running aws ec2 describe-volumes --volume-ids <volume-id>.
  • Policy Scan: This policy is reactive and checks during execution, not on a schedule.

Triage​

What is the impact if it is unfixed?

  • Keeping io1 volumes may lead to higher costs and potentially lower performance.

Does this problem get worse over time if it is unaddressed?

  • Yes, as newer volumes require enhanced performance and cost-efficiency.

Can remediation cause outages or downtime to any other running service?

  • Migrating a volume may require planning to avoid downtime; snapshot and restore procedures can help mitigate this risk.

Act​

What do I do to fix this alarm?

  1. Create a snapshot of the current io1 volume.
  2. Create a new volume from the snapshot with io2 type.
  3. Detach the old io1 volume and attach the new io2 volume to the instance.

Reflect​

What should I do if this alarm wasn't a good use of time?

  • Review and adjust the threshold or disable the policy if not applicable.