So let's find out why GuardDuty is the spendiest @awscloud service in one of my AWS accounts for January.
Okay, a crapton of CloudTrail events. Hmm.
This account is part of an organization. I'd have expected this to show up either in the CloudTrail bucket account, or the org payer management account.
GuardDuty console in this account confirms it.
Daily GuardDuty cost is fairly spikey.
Okay, this makes some sense. It's a "legacy" account that predates my adoption of Control Tower. Instead of sending cloudtrail logs to the central logging / audit account, it's using its own.
And there's a bunch of stuff in this account.
The first management event trail is free. Cool! The second would cost me ~$6.50 for this, which is also fine.
Why is GuardDuty costing 4x that?
Well that'd do it; GuardDuty analysis of the CloudTrail events is 4x more expensive than the CloudTrail cost would be (disregarding the first free trail, obviously).
Now, wtf is causing that many events without showing up on the bill?
Time to click the suspicious and frightening "Create Athena Table" button.
And this thing tells me that it's a third party vendor I was playing around with making 9.6 million queries against the account so far this month. Somehow I'm only being billed for 6 million of those in GuardDuty. Hmm.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
And now, the Alphabet (Google's parent company) earnings call. It's the rarest of unicorns: a YouTube video that doesn't whine at me to upgrade to YouTube Premium.
The market is happy. Stock up 7.5% in after hours trading.
I've repeatedly said that if I were going to start a company from scratch today and I didn't have a pile of experience with @awscloud, I'd be hard pressed to choose a cloud provider who wasn't @googlecloud.
I stand by that, but let's bound this with the reality that I *do* have that experience with AWS.
If I'm building something for production, where downtime is going to have a real impact to my customers and to my business, it's borderline unthinkable that I'd pick a provider that isn't @awscloud.
It took me a while to figure it out, but the reason I adore @b0rk’s content is that she excels at approaching explaining things in a way I can only aspire to. A thread…
Her latest is a great example of what I’m talking about. Go read it, then come back.
Think of basically every other ipv6 advocacy piece you've ever read. They all round to "here's why it's good and you should use it," usually with a helping of "you ignorant jackass" sprinkled throughout.
If you had given me 200 guesses about which company just pulled a “hey fuckstick, we’re turning on a chargeable service for your account because fuck you” I would not have guessed @awscloud.
Clearly times are changing and so must my impressions and opinions about the company.
Yeah, it's not going to impact a bunch of folks financially, but this is the first time I can *ever* recall that "configure something in AWS, leave on a trip for a decade, and come back to a higher monthly bill" has been true for any customer.