With zero commentary on the technology itself, in this thread I’m going to bring web3 culture to @awscloud concepts.
Every API call you make becomes a chargeable transaction.
Every time you mention a few key terms you'll get @AWSSupport lookalikes replying instantly with sketchy Google Doc forms claiming to be the support portal and demanding your credentials. Twitter will do nothing about this.
If you lose your MFA device / root credentials, you’ll be billed every month for the rest of time on whatever’s inside your account.
If you mention that you're not using DynamoDB, I'll condescendingly reply with "ngmi"
Every few days there will be another story about how someone got their IAM credentials stolen and they're now liable for $200M in EC2 charges. “This is good for @awscloud” will be the refrain.
Data egress to the internet will cost 6x as much as storing the data—wait. That one actually happens in @awscloud. Maybe they should call it "gas fees" instead of egress.
If you adopt a "wait and see" approach to the technology you'll be constantly hounded by people trying to convince you otherwise.
The "data centers 4 life" crowd will be every bit as obnoxious as the cloud advocates.
Your profile picture can now be an AWS architecture diagram logo for your favorite service. They will mean nothing to anyone not deep in this space. And the art will remain terrible.
Every AWS service will be described in a context that makes it completely unclear what the hell business value it provides, instead of just SageMaker.
Every transaction shows up in the ledger/bill, but it takes a day to process. This is considered to be just fine.
We’re all going to start putting CloudFront POP designations in our usernames.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
In today's episode of "ways Amazon is attempting to scam customers," the default option for a book purchase I was attempting to make is apparently to instead rent it. Caught it in time to cancel the order.
This is increasingly a company whose best days are behind it.
I miss the days when the bookstore part of Amazon was focused on adding value to the customer instead of literal rent-seeking.
"Triple check that you're buying what you THINK you're buying" was never something I had to concern myself with.
Note that the buyout price that they emailed me was significantly more than the price to purchase outright.
As a customer, how do you imagine I feel looking at this? Do you believe this earns trust? Do you think I'm likely to spend MORE with Amazon now?
I've been told that since enough has changed in how I do podcasts / video work, I should do another thread about my A/V setup (equipment and software) here at home.
Let's start with the audio path.
This is an ElectroVoice RE20 mic with a pop filter and a shock mount on it. I've been using it for a while; it's on a Røde mounting arm.
It plugs into the Cloudlifter mounted to the underside of the desk. Exciting. No buttons, so out of sight, out of mind.
Ooh, I can retitle it. Yes, this is real, not me having fun with the browser developer tools.
I use this account as my AWS credit dump; I'd prefer the opportunity to tell these things to ignore credits and tell me what it'd be costing me in actual dollars if we disregard the company scrip.
Let's build something new: a screenshot repo with a custom domain. Datastore is S3, DNS is CloudFlare. Eeny meeny miney Pulumi. @PulumiCorp, you're up.
They have a handy "S3 static site" tutorial option. It's in JavaScript, with a link to the Python code. Nice!
The first command errors. Less than nice.
(It wants `pulumi new` first).
They offer sample code on GitHub. This is why I have @cassido's keyboard handy.
One of the joys of being a publicly traded company is that Amazon gets to (read as: must) file a bunch of annual reporting information, in the form of a 10-K filing. In this thread I'll read through it and summarize the interesting @awscloud bits.
Amazon thinks about its business in three segments: North America, International, and AWS.
The Alexa org presumably yearns to break free into its own business unit.
I've talked in depth previously about Amazon's post-employment non-compete agreements. They're scoped to all of Amazon.
Over the weekend I somehow hit 80K followers on this site, which is just wild to me. Five years ago I started with something like 2K, and that had taken me seven years to scrape together.
Some things I have learned along the way as the audience has grown.
There were never any real "giant surges" that led to gaining 10K followers in a week or anything like that. It was about consistently being me.
My relationship with the site has changed as well. I used to be much likelier to put any thought that crossed my mind onto Twitter.
There are inflections that come with a larger audience. There's remarkably little I can tweet these days that SOMEONE won't take issue with.