I have permission to go on a bit of a rant about this tweet-question, so let's get right to it.

I've heard of worse ideas but not recently. A thread.
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.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Corey Quinn

Corey Quinn Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @QuinnyPig

21 Jul
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.
Read 4 tweets
20 Jul
I've been hoping someone would build something like this to show relative @awscloud service costs. A thread!
"Why not you?"

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.
Read 8 tweets
19 Jul
Okay, first @awscloud recruiting outreach to the newsletter email address. That wins points!
(Just for clarity: nobody at AWS recruiting has done anything wrong here. I'm just amused at how much of a terrifying corner case I am.)
I promise you, there is no (reasonable) checklist item for "has this candidate built a business on top of making fun of our shortcomings."
Read 4 tweets
16 Jul
So @FarrahC32 is a relatively new @awscloud employee and mistakenly believes that people know she works there because of her badge.

In reality, that's not how people know you work at AWS. A thread!
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.
Read 16 tweets
15 Jul
Customers: Fix your cross-AZ data transfer pricing, it's killing us.

AWS: Here are four more ways to run containers!
Customers: We'd really like to understand how all of these services interact together.

AWS: We've scheduled re:inforce and the Americas Online Summit for the same days!
Customers: I live in fear of the free tier billing me.

AWS: You set up a Managed NAT Gateway and now you owe us approximately "Guam."
Read 5 tweets
15 Jul
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.
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(