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.
So these containers (up to ten) live on a VM within a region. Sadly, there's no straightforward way to figure out which AZ that VM lives within.
"But @awscloud manages it for you! Why would you need to know or even care which AZ it lived--oh no."
Oh yes.
Data transferred to/from *SOME* @awscloud resources will cost you nothing, whereas data transfered to/from *OTHER* @awscloud resources in the same region will cost you 2¢ per GB. And once again I break out my data transfer pricing chart.
I'm not suggesting that 2¢ a GB is going to wreck me for any *reasonable* use of Cloud Shell.
But I am suggesting that crossing the boundary from "free" to "not free" changes user perception, and should be done thoughtfully--not because pricing models are hard.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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.
It's the AWS infrastructure keynote with Peter DeSantis, and this is my #reQuinnvent livetweet thread. Like an @awscloud groundhog, this is the one day a year he comes out of the data center to tell us what he's seen, look for his shadow, and use the bathroom.
♪ ♫ ♬ He's coming out of his cage, and he's feeling just fine... ♪ ♫ ♬ #reinvent
Music in a minor key about adversity is a great choice to kick off a keynote about infrastructure. Hardware is always depressing; it's a real kick in the rack nuts. #reinvent
So here's an @awscloud Lambda@Edge problem that's haunted me for ages. A thread, as I thrash and attempt to learn the things I don't know...
Curling the official @awscloud status page takes .3 seconds to complete. If I curl stop.lying.cloud, that takes 23 seconds to complete. And it absolutely should not.
The domain points to a CloudFront distribution. That distribution invokes a Lambda function that returns HTML with my suitable modifications to the payload.
And now the Data Analytics leadership session at #reinvent--oh what the damn hell. @rahulpathak didn't dress up for our podcast recording nearly so well!
This entire slide also applies to the @awscloud bill.
"Here's how Moderna uses our services to fight the pandemic, so you can feel better about using those same services to show ads to people."