cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Champion

Postmortems on pitfalls of automation at scale.

Periodically, one (or more) global cloud service providers sneeze and the panic ensues.

Given that many of modern communication channels and platforms rely on a single chosen cloud provider, the impacts of these events have much larger footprint than people tend to realize.

 

There is also an inverse relationships, such as one that manifested itself when DYN was DDOSed in 2016

https://en.wikipedia.org/wiki/2016_Dyn_cyberattack

 

The latest one is brought to you by courtesy of Google and you can read about it here:

https://arstechnica.com/information-technology/2019/06/the-catch-22-that-broke-the-internet/

 

One of the mandatory steps that I am taking when assessing the survivability of the infrastructures and enterprises, involve tracking down and documenting the dependencies of the Anything aaS.

 

It pays to invest time into it to prevent the "Oops" moments such as the platforms and the users of GCS have experienced and have contingencies planning in place.

1 Reply
Contributor II

Re: Postmortems on pitfalls of automation at scale.

The technical postmortem write-up for GCP can be found here: https://status.cloud.google.com/incident/cloud-networking/19009