I'm having a strange issue with one of my RDS databases where both `EBSIOBalance%` and `EBSByteBalance%` dropped to zero while I was running a data migration script. I'm using a `t4g.small` instance with gp3 storage that has the default provisioned IOPS set to 3,000 and a throughput of 125 MiB/s. However, when I checked the CloudWatch metrics, I noticed that my actual usage was quite low—only about 400 IOPS per second and 9 MiB/s throughput, which are well below the configured limits.
I discovered that the instance type can limit EBS performance as well, so I looked at the AWS documentation for `t4g.small` and found out that its performance limits should allow me much more than what I'm experiencing. I'm confused as to why the balance metrics dropped to zero when I'm not hitting the instance-level limits. Does anyone have insights into why this might be happening? Thanks in advance!
1 Answer
I've been there too! These EBS issues can really throw a wrench in your plans. You have a couple of options: either upgrade your instance type to something that can handle the load better, or consider switching to serverless with unlimited IOPS. We made the switch and it really helped us.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures