How we designed Cedar to be intuitive to use, fast, and safe
Blog
This article explains how Cedar, an open-source authorization policy language, was designed with three core principles: usability, speed, and safety.
- Cedar uses default-deny semantics with forbid policies overriding permits
- Authorization decisions are order-independent and provably correct
- Policies are written using application-specific vocabulary for intuitive readability
- Entity hierarchy and attributes support both RBAC and ABAC models
- Structured syntax with scopes and conditions enables scalable policy evaluation
- No loops or stateful operations ensure fast evaluation and bounded latency
- Typical authorization latencies are less than 1 millisecond
- Used by AWS in Verified Permissions and Verified Access services
Cedar decouples access control from application logic, enabling reusable, auditable authorization policies with proven correctness and high performance.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.