They conveniently provide no detail about the usecase, so it's hard to tell
But, yeah, there's certainly a solution to provide better performances for cheaper, using other settings/services on AWS
But, yeah, there's certainly a solution to provide better performances for cheaper, using other settings/services on AWS
In those cases, it is great to a) not get a shocking bill, and b) be able to somewhat support this atypical use until it can be remedied.
I'm honestly quite interested to learn more about the usecase that required those 50k API calls!
I've seen a few cases of using S3 for things it was never intended for, but nothing close to this scale