How to implement relationship-based access control with Amazon Verified Permissions and Amazon Neptune

This article discusses how to implement relationship-based access control (ReBAC) using Amazon Verified Permissions and Amazon Neptune. ReBAC is an access control model where authorization decisions are based on the relationships between the principal requesting access and the resource being accessed.

Specifically, the article covers:

• What is ReBAC and its benefits over traditional access control models like RBAC and ABAC
• Common relationship models in ReBAC like resource ownership, resource hierarchies, and user hierarchies
• An example scenario for a video application implementing ReBAC
• Overview of the ReBAC application architecture using Verified Permissions and Neptune
• Data modeling and graph queries in Neptune to represent and traverse relationships
• Cedar policy design for ReBAC policies
• Structure of authorization requests to Verified Permissions with relationship data
• How to combine ReBAC policies with ABAC policies using Cedar
• Conclusion summarizing the implementation of ReBAC with Verified Permissions and Neptune