Brutkey

Jess👾
@JessTheUnstill@infosec.exchange

"Business Continuity Planning" isn't just about "US-EAST-1 went offline, how do we manage fail over and uptime". It also includes things like "this whole platform has been discontinued/gone bankrupt/KilledByGoogle/quintupled in price/been MegaBreached, how does my business/project survive?"

firebreathingduck
@firebreathingduck@social.vivaldi.net

@JessTheUnstill@infosec.exchange

We live in an age of Cover-Your-Ass engineering. I would bet almost all of the people in charge of business continuity across the entire industry approach the problem this way: "If both the primary and backup cloud regions we use are offline, the business will hemorrhage cash but I personally won't be blamed."

It's another form of "Nobody ever got fired for buying IBM."

My tiny employer has a sub $5k/month cloud bill on AWS. If we were bigger, I would be pushing for moving to two or three independent smaller providers spread across at least two continents. That solves the actual problem, not just shielding me from blame.

Jess👾
@JessTheUnstill@infosec.exchange

@firebreathingduck@social.vivaldi.net And a number of other cloud hosting providers do offer a relatively smooth AWS migration pathway - like try to be almost as API compatible as possible for the main services like EC2 and S3 and whatever. So it certainly wouldn't be impossible. But it does involve actually understanding your environment and where the dependencies are.