SIGv4 means that every single request is authenticated. This is different from "encrypted." It makes sure that you are you.
"Starting last week, as part of S3 Multi-Region Access Points, we’re using a new version of AWS SIGv4, called SIGv4A"
An @awscloud product manager thought "sig vee four" flowed off the tongue too easily and would very much like to be promoted to Principal Namer.
The old things always knew what region a request was going to, which is part of how it works. AWS built a new thing that can field requests destined for multiple regions, which breaks the model.
Customers have an audit log because math. Like most math, it takes "doing the problem on the blackboard" kind of time to show up in the audit log because CloudTrail.
If you were making this request in a web browser, you would get the reassuring padlock in the address bar.
Some AWS customers find tin foil hats to be very fashionable.
The customer's request is turned into a long string that contains the request, the time, the algorithm, a copy of their AWS bill, etc.
"I could build a better @awscloud for less money" remains the rallying cry of fools.
If you get a (decrypted) packet capture of the request, you will almost certainly wish to curse God and die.
Instead of weakening security protections, @awscloud removed the region constraint and balanced it with additional cryptographic proof of who the customer is.
Your laptop might smell like burning metal even after you quit Slack and Chrome. AWS very much regrets not charging for IAM even more than they did at the start of this thread.
In conclusion @colmmacc is almost certainly better than you are at this, but is putting himself out there in public so that his technical peers at competitors can absolutely savage him if anything he has said is untrue.
That is not me, but nothing he has said is untrue.
In conclusion "this stuff is profoundly difficult and you generally don't have to think about it at all, but you might need to upgrade your laptop."
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So many years ago, when my humor was significantly more sophomoric, I had the “cloud to butt” browser extension installed.
It replaced the word “cloud” with “butt.” Suddenly @redhat’s site was talking about public and private butts, which admittedly makes a lot more sense than whatever the hell it’s talking about now.
I was embedded at a client site for a while, and I replied to some email or another. The client manager responded with what might possibly be the most flustered email I’ve ever read, apologizing for his previous message.
Every time that I've looked at them prior
I found two big things to correct:
The first rooted within architecture
The other its shitty DX
For the former it seems kinda squirrelly
For a database to think that it's somehow a queue
And the latter with console or CloudFormation
ERROR: ROLLBACK_IN_PROGRESS: FUCK YOU
So an anonymous Twitter person DM'd me this morning with a scenario. "I work at a large cloud company that makes inscrutable naming decisions, and I have an offer elsewhere for 35% more. Should I take it?"
Oh good heavens yes. A thread...
I hopped on a call with them and proceeded to firehose a bunch of career advice in their direction. I took a few notes and here's the gist of it.
No one is going to have your interests first and foremost except for you. You owe your employer a duty of care, and a duty of confidentiality, but you don't owe them loyalty.
Stage 0: You have an idea. You fit in the free tier.
Stage 1: You get a pile of Activate credits (anywhere from a pat on the head to $100K, though there are exceptions). This counterintuitively helps set you up for failure; if it's "free" to you, you don't practice good early hygiene.