Clients shouldn't know bucket names, regions, or AWS accounts Access should be fine-grained (specific packages, not entire buckets) Authorization should be efficient (not re-evaluated per file) Data locations should change without breaking client code Traditional S3 approaches fail...
ALDA: You say thinking is a kind of inquiry. Most of us think thinking is… you know… having thoughts. / PEIRCE: That is like saying digestion is having food. The interesting part is what happens because something is indigestible.
“So the denotation of the capability… is the capability itself.”
Explain how SDA is like being able to “eat the menu;” as a Roald Dahl story.
The hotel is a metaphor, but the system is precise. // This is how you build a **logical S3 bucket** that: / - hides physical layout / - spans regions / - supports arbitrary collections of objects / - requires no PDP at request time / - and does not give clients bucket access…
The Machine hums. / Miles of YAML scroll past on glass walls. / Policies reference policies that reference policies. / Everything technically works. / Nothing is understood…
Schmitt: / And sovereignty appears only where it belongs: / at the boundary of legitimacy, not inside every action…
When judgment retires upstream, enforcement gets simple, guards get happy, and Jerry gets the cookie
Head-to-head Euchre: burn four cards, race to 10 points, and dealer always scores for turning a Jack.
Against the suspicion—already present in Plato—that truth lives elsewhere, Aristotle teaches us to stay. / He does not ask us to look past things, but to look long enough. / In doing so, he restores dignity to attention itself. / The patient gaze becomes a moral act…
iHack, therefore iBlog 
You must be logged in to post a comment.