Wanted to get the communities opinion on a widget I have for validating gp3 volume savings.  AWS announced gp3 volumes back in December 2020 as a way to get great EBS performance with a savings of 20% as compared to gp2. https://aws.amazon.com/blogs/storage/migrate-your-amazon-ebs-volumes-from-gp2-to-gp3-and-save-up-to-20-on-costs/.  The quick math on that was that gp2 volumes cost $0.10/GB-Month   and gp3 volumes cost only $0.08/GB-Month.  There is a 'gotcha' if your EBS volumes exceed the I/O and bandwidth defaults and extra charges will apply.

To see how our cost savings are working out with gp3 volumes,   I created a simple widget that shows EBS cost as a percentage and group by the item description.  Filter for EBS  Service, and item description contains "gp3", and adjust the Y axis to start at 75%.  The idea is that if my 'extra charges' for excessive I/O and bandwidth exceed 20%, then perhaps gp3 was not a good choice, and additional research is required. Attached is a sample graph of an application that has gotten "busy" in recent months, and now the I/O and Bandwidth charges are starting to exceed more than 20%.