DEV Community

Anushka B
Anushka B

Posted on • Originally published at aicloudstrategist.com

gp2 gp3 is the easiest ₹50K/mo you'll ever save

gp2 → gp3 is the easiest ₹50K/mo you'll ever save

The easiest AWS cost win nobody takes: migrate gp2 to gp3.

Why nobody does:
→ "We'll plan it next quarter"
→ "Migration always has risk"
→ "We need to test first"

Reality:
→ gp3 has the SAME IOPS baseline as gp2 (3,000), and you can scale independently for more
→ gp3 is 20% cheaper per GB than gp2
→ The migration is zero-downtime. Literal one-line CLI: aws ec2 modify-volume --volume-type gp3
→ Snapshots, attachments, everything carries over
→ Takes 10 minutes per volume, most of which is AWS internal copy time

For a typical Series B SaaS with 100 EBS volumes at ~3TB total:
→ gp2 cost: ~$300/mo (₹25K)
→ gp3 cost: ~$240/mo (₹20K)
→ Savings: ₹5K/mo, ₹60K/yr

At larger scale (50TB+ EBS footprint), this becomes ₹30-50K/mo savings. Zero effort. Zero risk.

The fact that 68% of AWS accounts I audit still have gp2 as the default volume type tells you something: cloud cost optimization isn't a technical problem. It's an attention problem.

The 10-minute weekly ritual that saves more than most "cost optimization tools":

→ Monday 4pm: query all gp2 volumes above 100GB
→ Run modify-volume for each
→ Update IaC templates so new volumes default to gp3
→ Next Monday: confirm

That's it. ₹50K/mo for most mid-market teams. No migration project. No RFP.

If someone on your team is "planning" this next quarter, repost and tag them. It's this Friday afternoon, not next quarter.

AWS #FinOps #DevOps #CloudCost #IndiaSaaS #Engineering #EBS #Infrastructure #Founders

Top comments (0)