Let me point out some cloud magic tonight / say some nice things.

Normally I dunk on @awscloud in these threads, but today that puts me Nazi-adjacent. Plus AWS marketing's nerves are a little... frayed, so I fear for my safety.
The easy starting point is @awssupport. People are just rude as hell to them and they take it on the chin like the professionals they are. "Amazon is owned by a billionaire!" but he doesn't have to field the support tweets.

They also have to figure out when I'm trolling.
No matter how much you complain, they'll help you out. They're marvels, and good people too.
Adjacent to this is AWS's training group. Go check out the AWS product page. It looks like I'm trolling you, right? That horror is *real*!

They teach people to understand all of this--repeatedly. That's no small thing.
The AWS network is likewise magic. Ever notice how in datacenters the top of rack switches like to melt?

Ever notice how you can get full line rate to basically all of your instances all of the time?

Now think of those two things at once and marvel.
Once upon a time, failed hard drives were a "call the datacenter flunky" open ticket item.

Today failed hard drives are an easy-to-miss incredibly brief latency spike. Realize it's been years since you actually cared about SMART.
Behold a series of storage systems, all of which offering you linear pricing on infinite storage.

"Storage isn't infinite!" you might say. It's more infinite than your budget is, I promise.
I complain that us-east-1 has 392 different EC2 instance types/sizes between which you can choose, but that also means that no matter what your workload looks like, there's an instance that'll fit it like a glove.
Some recent things: VPC Reachability Analyzer. S3 Storage Lens. gp3 volumes. All of these are things you should have in your back pocket for when you need them.
Even with their enormous global footprint, there has never been a global network control plane outage for @awscloud in fifteen years. Not once.

The exception case you're about to respond with isn't one of them.
They consider APIs to be promises. Anything you had that worked to provision services in 2009 will still work today. The services are all still there.
I escalate weird customer issues to @awscloud service owners fairly frequently because I neither understand nor respect boundaries.

None of them have ever asked how big the customer was, because it didn't matter.
If you build a site on @awscloud and then leave (set it to autopay first!) for five years, you'll come back to a site whose infrastructure is more reliable, better performing, and less expensive.

Meanwhile the raccoons dismantled your data center.
Have you really stopped to think lately about the idea that you can spin up a world-ranked supercomputer for as long as you need it and no longer, pay for it with a credit card, and then turn it off and be done with it?

That still blows my mind.
People love to complain about service limits, but without them I'd be on the phone with @awscloud three times a year sweating blood that they're going to forgive a typo that cost me $200 million.
I whine and complain an awful lot about @awscloud services. Truth is, 95% of it is awesome, so I don't bother talking about them. It's become a utility; you don't question whether water will come out of the faucet when you turn on the tap.

• • •

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

14 Jan
This will sure show @awscloud! No way they'll be able to create Amazon Elasticsearch a... second time.
Yes. That is exactly the *point* of open source. Don't like it? That's valid! Don't go open source. But to claim that @awscloud and others are somehow doing something underhanded is just flat out incorrect. Image
As @vmbrasseur points out, using @elastic or Kibana are now actively business risks that your company needs to manage.

anonymoushash.vmbrasseur.com/2021/01/14/ela…
Read 4 tweets
14 Jan
And now a livetweet thread of a legal conference in the case of C21-31-BJR, Parler LLC v. @awscloud.
Parler suggests "AWS just has to flip a switch and Parler gets turned back on. Parler has been their customer for 2.5 years."
"They've met and conferred over some user content that violates not only Parler's user requirements, but also Amazon's." Yes, they'll do that, whether you want them to or not.
Read 29 tweets
14 Jan
This one grabbed my attention. I spent two years at @TaosTech. They’re the reason I moved to SF, started my own consulting firm, and met some wonderful people. It’s probably the best job I ever had.

Very savvy move by @IBMcloud.
I have a request to say more. Well okay!

The @TaosTech technical interview is a thing of genius. It's standardized, modeled after SAGE levels, and reshaped how I think about hiring engineers.
At the time my biggest gripe with Taos was that they didn't have a role into which I "fit." With the benefit of hindsight that's not their fault; I don't fit in anywhere, which is why I'm here.
Read 7 tweets
13 Jan
I read this tweet aloud to my wife.

@bequinning: “Oh, Ambika?! We went to law school together!”
I always wondered how an attorney would frame "cool story, bro" and now I know.
I'm starting to think that maybe the Parler folks might not fully grasp how complicated web properties work.
Read 5 tweets
13 Jan
In this thread (which you may want to mute), give me a company and I'll tell you why they fired me.

I'll start with @F5: because I used the word "refreshing" in their marketing copy.
I felt sorry for the princess our customers had to kidnap for ransom to pay for our product, so I bought her a taser.

I violated their ethics policy by having some.

Read 73 tweets
12 Jan
There's been a lot of noise lately about follower counts, so I'm pleased to leap into that and take a remarkably petty victory lap:

I now have more followers than the hardest working account in cloud, @AWSSupport.
Their milquetoast advice will work, but my terrible advice is way better!
@AWSSupport: "Use RDS as your database!"
Me: "Use Route 53 as your database!"
AWS: "Lock down your S3 buckets to avoid data leaks."
Me: "Save money by storing data in other people's insecure S3 buckets."
Read 5 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!