Skip to main content
Rightsizing · Low severity

EBS gp2 to gp3 Migration

On a gp2 volume performance scales with volume size, while gp3 provisions performance independently of size and prices it up to 20 percent lower.

Free to start. No card. The playground just needs your work email.

AWSprovider
Lowseverity
Savingswhere it shows up
Guidedfix, after a review

AWS

Found, explained, fixed.

Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.

01

Detect

ZopNight checks this automatically across AWS, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Change EBS volume type. Where the saving can be proven it is priced; where it cannot, the finding says so.

03

Fix

After a guided review, where you confirm the change, ZopNight resizes it to the recommended tier, then checks the change took.

Applies to
EBS Volumes on AWS
The fix, by hand
  1. Open EC2 → Volumes → select this volume → Actions → Modify volume.
  2. Volume type → gp3. Leave IOPS and Throughput UNSET. ModifyVolume preserves your current performance (it provisions max(current, gp3 baseline of 3,000 IOPS / 125 MB/s)), so a volume already above baseline keeps its higher IOPS/throughput. Any above-baseline cost is already netted into the saving shown. Only enter explicit values if you intend to CHANGE performance.
  3. Click Modify. The change takes effect online; the volume stays in-use with no downtime.
  4. Monitor CloudWatch VolumeReadOps / VolumeWriteOps during the migration to confirm I/O stays healthy.
  5. Once state returns to 'in-use', verify your application is still performing normally.

ZopNight does this for you after a guided review.

Category
Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
Where it appears
The Savings tab of Recommendations, with every affected resource listed.
Rule ID
RC-020
Full reference

EBS gp2 to gp3 Migration

Related checks

See the oversized resources in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·