Skip to main content

Triage AWS EBS Volume Size EBS_VOLUME_HIGH_SIZE

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

Triage Guide for EBS_VOLUME_HIGH_SIZE Violation

Understand​

Large EBS volumes can be expensive and might indicate improper resource allocation. Investigate whether the resource usage justifies the size.

Validate​

  1. Why should I care about fixing this issue?: Large volumes incur higher costs and could indicate inefficient resource use.
  2. How am I sure that this alert is true and accurate?: This policy uses AWS DescribeVolumes API to get the actual size of the EBS volume. Verify the size in the AWS Management Console.
  3. Does this policy scan on a schedule or is it Reactive?: This policy scans on a schedule, running once daily.

Triage​

  1. What is the impact if it is unfixed?: Rising costs and potential underutilization could lead to budget overrun.
  2. Does this problem get worse over time if it is unaddressed?: Yes, continued high costs with unused or underused resources.
  3. Can remediation cause outages or downtime to any other running service?: Reducing the size of an EBS volume might require creating a snapshot and provisioning new volumes, which might have minimal downtime.

Act​

  1. What do I do to fix this alarm?: Evaluate the necessity for the volume's current size. Resize or delete the volume if it’s oversized.

Reflect​

  1. What should I do if this alarm wasn’t a good use of time?: Adjust the size threshold or disable the policy if it's frequently alerting on justified volume sizes.