How Can You Scale It If You Don't Trust It?
summary
Argues that scaling requires engineering trust via enforceable, pervasive policy rather than paperwork or tribal knowledge, and shows concrete enforcement points: resource quotas, per‑protocol network rules, deployment gates tied to vulnerability scans, streamed log access instead of handing out SSH keys, and an inline proxy that issues ephemeral credentials and can drop destructive SQL or act as a circuit breaker. Reviews cloud and platform options (AWS, OpenStack/Congress, GCE limitations) and lists five capabilities needed for usable policy.
AI-written summary · about
chapters (6)
- 0:00Start
- 7:14Where's Your Policy Now?
- 8:41What Would Be Better?
- 15:30What did I leave out?
- 17:06Not from your cloud provider amazon
- 18:07Hopefully your platform?
related talks
27mHow can you Scale if you Don’t Trust It?
24mHow Can You Scale It If You Don't Trust It
22mLessons Learned from Scaling Infrastructure as Code
38mThe Dark Side of Scale
27mLeveraging Infrastructure as Code to Create Zero Trust Access to Your Apps and Infrastructure
27mTrusting Mission Critical Infrastructure: Building Reliable CD P...
33mScaling Infrastructure as Code
48mControlling Clouds: Beyond Safety