Tweet

@awssupport

This Thread may be Removed Anytime!

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

More from @QuinnyPig

Corey Quinn

@QuinnyPig

Mar 24

@okta

I have some sympathy for the @okta corporate comms team. After all, the @awscloud PR playbook isn't really an option for them.

But perhaps mine will be? A thread.

@acvisneski

I paid @acvisneski (my crisis comms consultant) to prepare a handbook for what to do in the event of an actual crisis. Chapter 1 may be of some interest: "Don't stick your dick in a pie." Let's read it together, much like I read my children bedtime stories.

And see, this is why she's the expert and not me; I've already run afoul of Step 1, "Don't refer to a crisis as sticking your dick in a pie."

Oops. So far, so good for you though.

Read 7 tweets

Corey Quinn

@QuinnyPig

Mar 23

@okta

And now, a live Zoom meeting where @okta's CISO Ray Bradbury talks about the breach.

"It's an embarrassment for myself and the entire Okta team." He's so incensed that he misuses the reflexive pronoun!

Taking pains to point out that Sitel is an external contractor. "It's not entirely our fault because we outsource dealing with our customers because we don't want to do it ourselves" isn't the strong statement it was workshopped as.

Read 11 tweets

Corey Quinn

@QuinnyPig

Mar 23

https://twitter.com/jschauma/status/1506459390160871432

Uhhhhh was I too credulous earlier?

https://twitter.com/jschauma/status/1506459390160871432

"We knew we were breached back in January but didn't think to check what the attacker may have done with that access" is how I read this. And reader, this is not a good interpretation.

How is it that I, a Cloud Economist whose secrets are arguably some of the most boring in the world, have a better comms plan in the event of breach than a bona fide security company?

Read 6 tweets

Corey Quinn

@QuinnyPig

Mar 23

@BMWGroup

The three hard problems in computer science are "cache invalidation," "naming," and "picking a cloud provider if you're @BMWGroup."

@awscloud

I mean, it's nothing short of breathtaking. We've got @awscloud, @azure, @googlecloud, @tencentcloud, @alibaba_cloud, @HPE, and @IBMcloud so far.

I mean, when's the last time you saw *that many* tags in a single tweet that wasn't shilling cryptocurrency?

Read 5 tweets

Corey Quinn

@QuinnyPig

Mar 16

@awscloud

Honestly, @awscloud giving self-taught learners free sandbox AWS accounts that are heavily restricted is a great thing for most people.

In my case it's like strapping raw meat to your chest right before you climb into the zoo enclosure to fuck around with the tigers.

@awssupport

Don't worry, if I run the AWS training and certification team's AWS bill into the stratosphere they can either ask for a concession from @awssupport or else engage The @DuckbillGroup for help!

"You know we monitor these for misuse, right?"

"Your version of 'misuse' is calibrated towards 'I use the account to mine cryptocurrency,' not 'I'm gaining nothing, but running up the AWS billing score.'"

"...I have to go make a phone call."

Read 4 tweets

Corey Quinn

@QuinnyPig

Mar 15

I'm tempted to do a Twitch livestream or something, but I feel old so instead this may be a very sad Twitter thread...

@awscloud

"Welcome to the island" says AWS Mustache. "On behalf of @awscloud, I mustache what you're doing here."

"As a new member of our IT staff, we invite you to do a speedrun through getting fired for making changes without management approval."

Read 38 tweets

Share this page!

Corey Quinn

People who liked this thread also liked...

Try unrolling a thread yourself!

More from @QuinnyPig

Corey Quinn

Corey Quinn

Corey Quinn

Corey Quinn

Corey Quinn

Corey Quinn

Did Thread Reader help you today?

Don't want to be a Premium member but still want to support us?

Like this author's thread?