Amazon Verified Permissions now supports the Cedar JSON entity format

Amazon Verified Permissions now supports the same JSON format for entity and context data, as the Cedar SDK. Developers can use this simpler format for authorization requests. This aligns the Amazon Verified Permissions API more closely with the open source Cedar SDK, and simplifies moving from the SDK to Amazon Verified Permissions or vice versa.

Amazon Verified Permissions is a permissions management and fine-grained authorization service for the applications that you build. Using Cedar, an expressive and analyzable open-source policy language, developers and admins can define policy-based access controls using roles and attributes for more granular, context-aware access control. For example, an HR application might call Amazon Verified Permissions (AVP) to determine if Alice is permitted to access Bob’s performance evaluation, given that she is in the HR Managers group. Customers can use Cedar JSON format to pass entity data describing the principal (Alice) and the resource (Bob’s performance evaluation).

This change is available in all AWS regions supported by Amazon Verified Permissions. The service will continue to support the old format, and so the change does not break existing application integrations. To learn more about using the Cedar JSON format, see Cedar JSON entity in the Cedar user guide and the Verified Permissions user guide. To learn more about Amazon Verified Permissions, visit the product page. For more information visit the Verified Permissions product page.