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.
After several attempts it makes everything somehow worse. @awscloud is now delisting it from the Marketplace until these bugs are resoled.
I appreciate my partnership with AWS and will say nothing untoward about them in public.
Yes, I *told* you that you could run this on your laptop before I sold it to you. I will now unleash an army of shitgibbons on the internet who will make fun of you unless your laptop somehow has 512GB of RAM.
I apologize that your profile photo is somehow set to compromising pictures of you fished from your camera's photo album.
Refunds are now available directly from AWS should you require one. Your patience continues to be appreciated.
Apple Silicon Macs have been available for all of 20 minutes but you're a complete idiot if you don't have one of them to run this script. True, I told you it would work on x86 machines, but let's get serious, who's still running one of those?
I have released another patch (40GB this time) that fixes the previous regression that started mining bitcoin in your AWS account. I apologize for the error and will strive to be more diligent in the future.
It turns out that "developer" and "publisher" mean different things.
This is all attributed to the same root cause as these tooling errors of "me not knowing what words mean." I am under a lot of investor pressure, you see.
It now appears that if your CURs become too large this script will irrevocably destroy them and you'll have to start over.
You are advised to use fewer resources in your AWS account.
GitHub has now made my repository private for some reason. I appreciate your patience while I work through these communication issues / reassure them that this isn't *technically* malware.
I wish to apologize for the reinforcement of deeply problematic views contained within this tool. How this even happened in the context of an AWS billing script will be addressed in the undetermined future.
The latest patch also removes the portion of the script that makes the loading dialog on the CLI trigger epileptic seizures--sorry, hold the phone on this entire thread.
They fucking *WHAT* in this shitpile game?! Are you serious?! Who the hell signed off on that?!
I think video games are a creative medium. I think they unlock a narrative viewpoint that's unlike any other, and should be celebrated.
I also believe they should not actively harm their players.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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?"
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.
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.