Skip to main content

Triage AWS EBS GP2 Volume GP2_VOLUMES

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

Triage Guide: GP2_VOLUMES Violation

Understand​

Why should I care about fixing this issue?​

Using GP2 volumes is less cost-effective and can result in inferior performance compared to GP3. Addressing this issue can reduce costs and improve performance.

Validate​

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

This policy uses AWS SDK to directly query your EBS volumes for their type. To validate this manually, you can use the AWS Management Console or AWS CLI to describe the volume.

What is the data source for this policy?​

The data source is the AWS SDK's DescribeVolumesCommand which directly queries AWS EC2.

How do I retrieve it manually?​

Using the AWS CLI:

aws ec2 describe-volumes --volume-ids [your-volume-id]

Look for the VolumeType in the response.

Does this policy scan on a schedule or is it Reactive?​

This policy is reactive and runs when a specific volume is observed.

Triage​

What is the impact if it is unfixed?​

Continued use of outdated GP2 volumes means higher costs and potentially lower performance.

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

Yes, as better alternatives are available, the relative efficiency and cost-effectiveness decline further.

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

Transitioning from GP2 to GP3 requires stopping instances that are using these volumes, leading to temporary downtime.

Act​

What do I do to fix this alarm?​

Convert the GP2 volumes to GP3 using the AWS Management Console or CLI.

aws ec2 modify-volume --volume-id [your-volume-id] --volume-type gp3

Reflect​

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

If this policy generated false positives or was not beneficial, you can adjust the policy thresholds or disable the policy as necessary.