So in tonight's thread I want to change things up a bit, and talk about things I like about @awscloud. Strap in.
First, the folks working in the tech field, including training and certification as well as @awssupport are miracle workers. I mean, think about it—they have to deal with you people!
IAM is complicated and tricksy, with dangers all about. The identity + security folks have what are functionally impossible jobs, but somehow they consistently deliver.
The EC2 console was *crap* fifteen years ago. Today it's simple, intuitive, and almost makes you forget the complexity masked within. That's a cloud UX turnaround story for the ages.
Route 53 is the only service with a (public) 100% SLA. That's damned impressive.
The containers and serverless folks: have you ever stopped to really consider just how magical "here's my code, run it for me" really is? We complain about the 5% gap while ignoring the 95% that's pure magic.
It's rare that a tool I've built is completely deprecated by a single @awscloud release, but the S3 Storage Lens did it. I couldn't be happier about it. Take a look if you haven't yet.
EFS went from "oh god why are they bringing NFS to the cloud" to a service I like and use myself. I really have no complaints left about it. I'm glad it's here.
The entire Systems Manager suite of offerings, while eclectic, serve to solve a whole raft of problems that once required large teams and expensive tooling to address poorly.
ACM means I no longer have to care about certificates expiring out from under me. Think back; how many site outages would that have saved you ten years ago?
Workspaces is one of those services I think is missing some of the recognition it's due. Why isn't this a household name? They're GLORIOUS!
There are others, but that's enough today. I sometimes fear that my snark about the gaps is mistaken for a dislike of the platform. Far from it—but nobody wants to hear a litany of praise for the stuff that works right every day. If they did I'd have a different job.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Before I start, this is my specific industry niche. It's nuanced, incredibly complex, and it's a near certainty that any issues I take with the report aren't criticisms of @martin_casado or @sarahdingwang at all.
Similarly, any VC criticisms I make are broad, not @a16z specific!
We start with this graph. Clearly something momentous happened in 2020 on a global scale: you forgot to turn your EC2 instances off.
Oh hey, to install RedHat OpenShift on AWS I have to grant @RedHat administrator access to the entire @awscloud account.
“You mean Administrator access to the ROSA service principals?”
No, I do not.
I should point out that this is significantly broader than AWS's own accesses into your account. You will have no secrets from RedHat if you do this. KMS keys? Theirs. Passwords? Theirs.
These are the only things RedHat can't do with that role:
Back up any personal (NOTE: NOT CORPORATE IP!) data on my work laptop whenever I get a context-less "let's talk" message.
Putting all of my corporate expenses on my personal card, then expensing them instead of the other way around to avoid giving them the "well technically this might be embezzlement" stick if they disagree with a decision.
It wants an S3 bucket. Cool. The service has one bucket for ingest, and one for output generally. Which does this form want?
ALWAYS WITH THE QUESTIONS, YOU PEOPLE!
"Encryption of S3 buckets is basically a box check for compliance groups. That said, we at @awscloud are going to mandate it for this service with your own KMS key because the KMS team bribed us for that sweet $1 a month revenue juicer."