The big problem that enterprises have is that the @awscloud bill is a game of Corporate Telephone between the person who receives the bill but has no context, and the person who can impact the bill who's five nodes away.
"Let's make sure that last person can never see the bill!"
Enterprise cloud deployments have their own fair share of problems, don't get me wrong. I just have a very hard time believing that "too many of our employees are looking at the bill" is in that list.
"Our discounts would be exposed to internal staff, and that's confidential!"
Yes. "How big of a discount you get from @awscloud" is exactly the kind of secret you can't trust to the people to whom you've entrusted admin access to production. Right.
Plus, let me level with you: in large enterprises, there are anywhere between 2-4 overlapping discount contracts. If you can reverse engineer the terms from the bill output alone, I would very much like to chat about your future job here at The @DuckbillGroup.
"I'm not convinced it makes sense, since we're not focusing on AWS bill optimization this quarter."
Okay. Okay.
1. That will change. 2. The bill is the only place you can see everything (billable) in your account all in one place.
There's a reason that one of our offerings here isn't just understanding these monstrosities, but *negotiating* them.
Look, I'm not saying that you need to expose everything to everyone. I'm merely suggesting that you should ideally be in a situation where telling someone "your cluster cost $20K last month" means that they know whether they're getting fired or promoted.
Ding ding ding. There's a reason that our Tableau bill is almost as much as our AWS bill.
An observation on legacy: I have never once heard a story about Jeff Bezos that made me say "he seems like a nice person."
@aselipsky? Too many times to count. @ajassy? Seen it myself firsthand.
But never Jeff.
You can never get a complete picture from the outside. I get that.
But you can absolutely get glimpses of the real person behind the public persona by talking to the people who've worked with them. Given enough data points, you can tie them together into a reasonable story.
The question is "how do you want to be remembered after you're gone?"
For me, I really hope the answer to that question isn't tied to my job, but instead the people I've encountered along the way.
I can't very well do it myself. At The @DuckbillGroup, our clients these days start at ~$1 million a month in spend or so. I'm very hesitant to give guidance to small accounts based upon what large ones are doing. It's a very slanted view of the industry!
That said, the data I'm seeing in here tracks with what I'm seeing in our client environments. As the post says, "this aligns with other cloud consulting organizations @getvantage has spoken to." We're one of them. They're spot on for the big items.
When you catch up with people you haven't seen since before the pandemic, you start off by handing them a document of what you worked on for them to read first.
Suddenly your favorite restaurant is "The Cheesecake Factory" because it's the only place that has a menu long enough.
DLP (Data Loss Prevention) is a failed industry and if you disagree you're almost certainly selling it.
So what is DLP?
Generally it's an appliance, software, etc. that makes sure that your employees don't copy sensitive data out of your environment.
Sounds good in theory, right?
In practice it's crap.
It has to MitM secure connections, so that's awesome. (A one stop breach!)
It has to recognize what the sensitive data is in the first place. (Is that a SSN or just a nine digit number?)
It has to work everywhere your sensitive data lives.