Well, that’s how AWS makes their money, they charge for every single disk operation, and it’s why AWS isn’t a viable solution for any medium to large medical group/practice, unless they have very high margins and a huge IT budget.
Remember, every user login and operation you do inside the EMR, may generate dozens of database queries and read/write actions. When you load a patient chart, save data, create/save/alter an encounter, perform an eRX transaction, send a message, run a billing report, etc, all those seemingly trivial things lead to multiple queries across multiple tables. Then include things like opening/viewing documents or patient ID images, it all adds up. Depending on how your database and storage are set up, 2000 requests as defined by AWS won’t go far at all.