Read on Twitter
Me trying to figure out how someone spent 440$ on Amazon Comprehend in the shared team account when our bill is typically 6$ a month...
OK. so I jump into the AWS Console for the team, and look at CloudTrail. Enabled by default on all AWS accounts. I can use CloudTrail to dig deeper. And, jackpot: (2/)
It& #39;s @benjamin_l_s! Part of the dynamic duo of AWS Serverless DA& #39;s in the UK. What is he doing.. good question. Diving deeper!! (3)
CloudTrail gives me pretty deep insight into whats going on here: (4/)
OK, so he& #39;s got something called "profanity checker" that he& #39;s running. if this is monitoring my tweets, its going to be active.. (5/)
quick pit stop to make sure that bucket isn& #39;t public...(it& #39;s not and we& #39;d get alerts if it were) (6/)
OK. the trail has run cold. The previous CloudTrail logs tell me the calls were from the UK where Ben is based. So probably something he was running locally...BUUTTTTTTTTTTTT the current bill tracking for the month seems to hint at a 900$ charge (and growing) month to date. (7/)
However I see no calls from Ben& #39;s account since Sept, until my own just now: (8/)
ok ok ok. I& #39;m learning more about Comprehend as I go. Where have I been? Well CloudTrail had no API call data between those two dates. I went so far as to export it all to Athena, and search there (it& #39;s a click of a button to start!!)
that was (9/). ok so that showed no data actually between the two dates in question. hrmm. let me go back to detailed billing reports. Wait, whats an "endpoint time"? (10/)
Well, the wonderful Amazon Comprehend pricing page is pretty straight forward. As are the docs. https://docs.aws.amazon.com/comprehend/latest/dg/create-endpoint.html">https://docs.aws.amazon.com/comprehen... (11/)
And back in the Comprehend console: (12/)
