How Netflix Is Solving Authorization Across Their Cloud [I]
summary
Netflix describes a cloud authorization system that runs an OPA policy engine in-process or as a sidecar, with an aggregator/distributor pipeline that pushes delta updates to hot agents, supports REST, gRPC, Kafka and SSH resources, and enforces policies in sub-millisecond latency (benchmarks around 10–20 µs and app tests under 0.2 ms). A UI generates Rego policies and stores unit tests with each policy so changes run tests before deployment, and the system is live across hundreds of teams.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:39Background - Definitions
- 2:08Background - Netflix Architecture
- 5:10AuthZ Problem
- 6:58Design Considerations
- 11:39High-level Architecture
- 15:07AuthZ Agent Internals
- 15:43Example Setup
- 17:56Open Policy Agent (OPA)
- 20:07Example Policy (in English)
- 20:26OPA: Rules
- 22:00OPA: Context-aware
- 23:15OPA: Composable
- 23:58OPA: Resource-agnostic
- 24:22OPA: Performance
- 26:25Capturing Intent
- 30:50Summary
- 32:26Take Away
- 34:21Questions?
related talks
35mOPA: The Cloud Native Policy Engine
38mOPA for the cloud natives
30mArmy of Proxies! How Netflix scales identity based zero trust...
42mDesign Patterns for OPA and Cloud Native Authorization
28mHow Netflix Makes gRPC Easy to Serve, Consume, and Operate - Benjamin Fedorka, Netflix
38mSecuring Distributed Cache: Achieving Secure-by-Default with Key Challenges &...
36mOPA for the cloud natives
33mIntro: Open Policy Agent
