EBS IO2 IOPS volumes are exceeding 64000 set limit


I have a t4g.xlarge instance type for my production server and have set 200 GiB and IO2 64000 IOPS limit, but am being hit 83000 IOPS and being charged $1200-$1300, so please suggest to me how to get the cost down suggest me a way to optimize it.

  • Not sure if I understood your setup right, but t4g.xlarge and EBS volume with 64000 provisioned IOPS just doesn't make sense. I don't think your instance can do even close to that, meaning you are paying a lot for IO performance you can not utilize. Baseline performance of t4g.xlarge is 4000IOPS (16kb) and at maximum it can burst 15700 for 30min/day. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html

  • we are being charged approx $4900 on 83000 IOPS, how can we sort things by bringing the price down in mumbai region.

1 Answer

A t4g.4xlarge has a maximum capability of 15700 IOPS so setting it to 64000 would be a waste of IOPS as you cannot use that many IOPs on the instance type. You can find a chart of maximum IOPS supported per instance here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html#current

What you should check is all of your EBS volumes to see what they are configured like. If you're being charged for 83000IOPS it's because you have disks configured to use that many IOPS as EBS for IO1/2 charges for storage, and configured IOPS. Take a look in the EC2 console at your volumes and see what disks are IO1/IO2 or GP3 and what their IOPS are configured at to understand where you're being charged from for the 83000 IOPS.

profile pictureAWS
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions