It directionally aligns with conversations I've had with a lot of folks internally. And the anonymous Amazonian raises a lot of points that honestly paint AWS in a pretty flattering light.
There are some problems with it, and there's basically zero chance they didn't unmask themselves. How many @awscloud cybersecurity folks use Sioux Falls as their shorthand for "Bumfuck, Nowhere," and turns of phrase like "Companies don't like to have their whole ass be shown?"
This is just patently false. Former Googler David Drummond had at least *TWO* families!
Wholeheartedly agree with this point. The "shared responsibility model" is a very careful corporate song and dance around the real truth of "if you get breached on @awscloud it's because *YOU* fucked up."
The idea of an AWS rep selling the security benefits of the cloud like this gives people apoplexy, but it's absolutely correct. Most data center security postures are dogshit.
("You'll save money" is of course an aspirational lie in practice, but that's okay.)
I didn't realize the Snowmobile (trailer full of drives for data migration) came with an armed guard. That's pure security theater. Data's encrypted on the trucks, what the hell kind of Road Pirate are they expecting to pull a heist?
While this is a funny line, it's incredibly dismissive of the entire entertainment sector as a whole. Do not agree.
This is actively terrifying.
The fact that Snowmobiles are import-only, not export capable is crappy. And it makes this section of the @awscloud product page actively misleading:
In all, my take from this is "AWS does mostly good things, the Amazon corporate parent is scary as hell." It's a good read.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It feels like it might be Thread of Uncomfortable @awscloud Truths time again.
Now that #reInvent has subsided, you get to choose between CDK, sam-cli, Serverless framework, Proton, Service Catalog, Service Catalog App Registry, and SAR.
Making that decision is way more entertaining than doing your job.
Now that AWS has begun naming services after things shouted on the factory floor (Lookout for Metrics/Equipment/Vision), next year we can expect "Who the Hell Parked in my Spot," a container pre-empting service.
I've decided I'm going to start selling software as if I were the Cyberpunk 2077 developers.
Please start by using my Stripe webcart to send me $70.
Okay, so the software I sold you *claimed* to help fix your @awscloud bill, but it crashes unless you run the script on FreeBSD.
I am very sorry for the inconvenience. Please stand by while I work on a patch.
After a lot of tweaking, this bash script now works on Ubuntu 14.04.
The patch itself is 22GB because I don't know what git-rebase does and I got sloppy with my git-adds somehow. Thank you for your business, please continue to be patient.
So @awscloud likes to make a big deal about "the first launch of #reInvent." Let's do something else: the last launch of #requinnvent. That's right, I'm dumb enough to launch a product during #reInvent.
Let's start by talking about cost management SaaS tools. A thread...
I've been on record for a while as saying that they suck, because they do. "Percent of your @awscloud bill" pricing, they try to do way too much (you don't use 90% of it), and they're all trying to be Expensive and Complicated Cost Explorer.
Worst of all, a tool can't replace a person in analyzing your AWS costs. There's no API for business insight, and attempting to install one into your staff apparently violates a bunch of laws.
And now, a nitpicker's guide to @awscloud's new Cloud Shell offering, announced today at #reinvent.
I was surprised and delighted to see it today. Yesterday, I was surprised and delighted to see the new console search.
Both product teams were apparently surprised but not so delighted to see each other.
Sadly there's no data on the persistence guarantee of that 1GB of storage. "THAT'S WHERE ALL OF MY PRIVATE KEYS LIVED!" shrieks the future customer with even worse workflow patterns than me.