AWS verifiedpermissions documentation change
Summary
Removed namespace limitations section and added note about alignment with Cedar's multiple namespace support
Security assessment
Documentation update reflecting feature parity with Cedar. No security vulnerabilities or security features are mentioned in the change.
Diff
diff --git a/verifiedpermissions/latest/userguide/terminology-differences-avp-cedar.md b/verifiedpermissions/latest/userguide/terminology-differences-avp-cedar.md index ca2f631cb..53ce30fa5 100644 --- a//verifiedpermissions/latest/userguide/terminology-differences-avp-cedar.md +++ b//verifiedpermissions/latest/userguide/terminology-differences-avp-cedar.md @@ -7 +7 @@ -Namespace definitionPolicy template supportSchema supportAction groups definitionEntity formattingLength and size limits +Policy template supportSchema supportAction groups definitionEntity formattingLength and size limits @@ -13,9 +13 @@ Amazon Verified Permissions uses the Cedar policy language engine to perform its -## Namespace definition - -Verified Permissions implementation of Cedar has the following differences from the native Cedar implementation: - - * Verified Permissions supports only one [namespace in a schema](https://docs.cedarpolicy.com/schema/schema.html#namespace) defined in a policy store. - - * Verified Permissions doesn't allow you to create a [namespace](https://docs.cedarpolicy.com/schema/schema.html#namespace) that's an empty string or includes the following values: `aws`, `amazon`, or `cedar`. - - +###### Note @@ -22,0 +15 @@ Verified Permissions implementation of Cedar has the following differences from +As of May 2026, Verified Permissions has aligned with Cedar and now supports multiple namespaces.