The Building That Runs the Cloud
A Letter From Eldad
For the people responsible for keeping the building running.
People talk about the cloud like it floats.
It doesn't. It lives in buildings. Big ones, full of chillers, pumps, batteries, generators, sensors, cameras and doors that lock.
Those buildings keep the servers alive. And most of the systems inside them now have a small computer. Software. A login. A network connection.
Most of those systems were bought by facilities. They're maintained by a vendor. They sit on a network IT runs. And they protect an uptime promise that operations owns.
Security often can't see any of it.
That creates a terrible choice at the worst possible moment. A cooling controller does something strange at night. You can leave it alone and hope it's harmless. Or you can cut it off and hope the server hall stays cool.
Neither is good enough.
This book is about a third option. See every device that keeps the building running. Know what each one can reach and what breaks if it stops. Take only the action you approved. Then check two things: the bad path is closed, and the building is still doing its job.
This is the fourth book in our series. The first was about hospitals. The second was about warehouses and supply chains. The third was about water. Different buildings, same question.
Can we contain the risk without causing the outage?
I wrote this for the people who answer that question at 2:00 a.m.: data center operators, facilities leaders, security teams and the executives responsible for keeping the service running. For colocation providers and AI cloud companies, the same question applies to the building systems their GPU workloads depend on.
Eldad Matityahu Founder and CEO, NetOps IQ