EBS volume uses gp2 — consider migrating to gp3
- Severity
- Info
- Service
- EC2
- Check ID
- EBS_GP2_VOLUME
What this check finds
gp3 volumes deliver the same baseline performance as gp2 at 20% lower cost per GB and allow independent scaling of IOPS and throughput without over-provisioning capacity. All gp2 volumes are candidates for an in-place migration.
Passing looks like: EBS volumes use gp3.
How to fix it
Modify the volume in-place — no downtime required for attached volumes.
AWS CLI
aws ec2 modify-volume --volume-id VOLUME_ID --volume-type gp3
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
EC2 → Volumes → select volume → Actions → Modify volume → Type → gp3.
Compliance
This is a cost check. It flags spend that buys nothing, which no compliance framework asks about, so it is not mapped to a control.
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More EC2 checks
- HighAccount does not block public sharing of EBS snapshots
- HighAMI is publicly shared
- HighEBS snapshot is public
- HighEC2 instance CPU spiked abnormally — possible compromise or runaway process
- HighEC2 instance has an IAM role with admin privileges
- MediumAccount default for instance metadata does not require IMDSv2
- MediumEBS default encryption is not enabled for this region
- MediumEBS volume is not encrypted at rest