EBS gp2 volume not migrated to gp3

An EBS gp2 volume that could be migrated to gp3 for lower cost and better baseline performance.

Last updated July 6, 2026

What triggers this finding

An attached or available EBS volume still on the gp2 volume type instead of gp3.

Modify the volume type to gp3 in place. No detach or snapshot is required for the migration.

About 20% lower per-GB storage cost compared to gp2 — e.g. $2–$20+/month on larger volumes.

See also: Severity and savings estimates for how Parsivex calculates figures on your report.

Plain-English definitions for all 13 Parsivex waste finding types, grouped by AWS category.

How to review warnings, use dry-run commands, test in non-production, and avoid destructive mistakes — especially with S3 lifecycle scripts.

How Parsivex prioritizes findings, calculates monthly savings figures, and why estimates are not guarantees.