Detect & correct EBS volumes with low IOPS

Overview

EBS volumes with lower than 16k base IOPS should be using gp3 rather than the more costly io1/io2 volumes types.

This query trigger detects io type EBS volumes with low IOPS and then either sends a notification or attempts to perform a predefined corrective action.

Getting Started

By default, this trigger is disabled, however it can be configured by setting the below variables

ebs_volumes_with_low_iops_trigger_enabled should be set to true as the default is false.
ebs_volumes_with_low_iops_trigger_schedule should be set to your desired running schedule
ebs_volumes_with_low_iops_default_action should be set to your desired action (i.e. "notify" for notifications or "delete_volume" to delete the volume).

Then starting the server:

flowpipe server

or if you've set the variables in a .fpvars file:

flowpipe server --var-file=/path/to/your.fpvars

Pipeline

Correct EBS volumes with low IOPS

Query

select
  concat(
    volume_id,
    ' [',
    volume_type,
    '/',
    region,
    '/',
    account_id,
    ']'
  ) as title,
  volume_id,
  region,
  _ctx ->> 'connection_name' as cred
from
  aws_ebs_volume
where
  volume_type in ('io1', 'io2')
  and iops <= 16000

Schedule

15m