EBS Provisioned IOPS Over-Allocation
Provisioned IOPS are billed per IOPS per month whether or not the workload issues them.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Lower the provisioned IOPS on the EBS volume. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
In one click, ZopNight resizes it to the recommended tier, then checks the change took. When someone other than an admin starts a pause or a delete, an admin approves it first.
- Applies to
- EBS Volumes on AWS
- The fix, by hand
- Review CloudWatch
VolumeThroughputPercentage/VolumeReadOps/VolumeWriteOpsfor peak usage patterns. - Reduce provisioned IOPS toward the observed peak (never below the 3000 gp3 baseline).
- Consider switching to gp3 if IOPS needs are under 16,000.
- Modify volume via EC2 Console → Volumes → Actions → Modify.
ZopNight does this for you in one click.
- Review CloudWatch
- 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-075- Full reference
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.