@lauriewired I found my two AWS accounts were bidding against each other sometimes. Without transparency about real availability(instance type and region) it's a bad market. AWS later switched to capping prices with unavailability rather than letting customer manage wild price swings.
@chanian right. part of the question is: "how would average sites defend themselves from this"? And the answer cannot be "you must have active secops equipped with closed, trusted frontier models"
fuuuuuuuck, whatever undergrad research assistant submitted this summary of their team's paper to phys,org, they knocked the headline out the goddamn park
I am annoyed that the AWS Well Architected framework pushes users to the multi-zone design. It's bound to end badly, though I'm sure it is great for AWS margins. https://t.co/dhgZeu8Vfe
I have been saying for a while that it doesn't make sense to invest in a multi-zone cloud architecture. Today I was proven right. Imagine every cloud user builds an application that can migrate between zones in a region with 3 zones A, B, and C.
As importantly, if you really want HA, test your architecture for failover. Flip your primary and secondary sites and back and forth regularly. It's expensive and time consuming, but anything less and you won't really know if your application can survive.
As a person who works in systems, infrastructure, and operations, what makes this twitter ordeal so fascinating is that no one has ever tried to take a huge system, get rid of all the engineers and see if it can really run itself. It's a unique experiment in resiliency.