AWS verifiedpermissions documentation change
Summary
Increased supported namespaces per policy store from 1 to 100
Security assessment
This is a quota increase without security implications. Namespaces help with entity organization but don't directly relate to security vulnerabilities or features.
Diff
diff --git a/verifiedpermissions/latest/userguide/policy-stores.md b/verifiedpermissions/latest/userguide/policy-stores.md index 0f9c6a9ef..d90cb5f98 100644 --- a//verifiedpermissions/latest/userguide/policy-stores.md +++ b//verifiedpermissions/latest/userguide/policy-stores.md @@ -15 +15 @@ We recommend creating one policy store per application, or one policy store per -We recommend using _namespaces_ to Cedar entities in your policy stores to prevent ambiguity. A namespace is a string prefix for a type, separated by a pair of colons (`::`) as a delimiter. For example `MyApplicationNamespace::exampleType`. Verified Permissions supports one namespace per policy store. These namespaces help keep things straight when you’re working with multiple similar applications. For example, in multi-tenant applications, using a namespace to append the name of the tenant to the types defined in the schema will make them distinct from their similar counterparts used by the other tenants. When looking at the logs for the authorization requests, you’ll be able to easily indentify the tenant that processed the authorization request. For more information, see [Namespaces](https://docs.cedarpolicy.com/overview/terminology.html#term-namespaces) in the _Cedar policy language Reference Guide_. +We recommend using _namespaces_ to Cedar entities in your policy stores to prevent ambiguity. A namespace is a string prefix for a type, separated by a pair of colons (`::`) as a delimiter. For example `MyApplicationNamespace::exampleType`. Verified Permissions supports up to 100 namespaces per policy store. These namespaces help keep things straight when you’re working with multiple similar applications. For example, in multi-tenant applications, using a namespace to append the name of the tenant to the types defined in the schema will make them distinct from their similar counterparts used by the other tenants. When looking at the logs for the authorization requests, you’ll be able to easily indentify the tenant that processed the authorization request. For more information, see [Namespaces](https://docs.cedarpolicy.com/overview/terminology.html#term-namespaces) in the _Cedar policy language Reference Guide_.