For more information about configuring, administering, and using Amazon Verified Permissions in your applications, see the Amazon Verified Permissions User Guide.
-For more information about the Cedar policy language, see the Cedar Policy Language Guide.
+For more information about the Cedar policy language, see the Cedar Policy Language Guide.
When you write Cedar policies that reference principals, resources and actions, you can define the unique identifiers used for each of those elements. We strongly diff --git a/clients/client-verifiedpermissions/src/VerifiedPermissions.ts b/clients/client-verifiedpermissions/src/VerifiedPermissions.ts index a9c3862ce661..978ac0ca1397 100644 --- a/clients/client-verifiedpermissions/src/VerifiedPermissions.ts +++ b/clients/client-verifiedpermissions/src/VerifiedPermissions.ts @@ -513,7 +513,7 @@ export interface VerifiedPermissions { * control (ABAC) authorization models.
*For more information about configuring, administering, and using Amazon Verified Permissions in your * applications, see the Amazon Verified Permissions User Guide.
- *For more information about the Cedar policy language, see the Cedar Policy Language Guide.
+ *For more information about the Cedar policy language, see the Cedar Policy Language Guide.
*When you write Cedar policies that reference principals, resources and actions, * you can define the unique identifiers used for each of those elements. We strongly diff --git a/clients/client-verifiedpermissions/src/VerifiedPermissionsClient.ts b/clients/client-verifiedpermissions/src/VerifiedPermissionsClient.ts index 8965ac5cd0d5..e303ac942b0e 100644 --- a/clients/client-verifiedpermissions/src/VerifiedPermissionsClient.ts +++ b/clients/client-verifiedpermissions/src/VerifiedPermissionsClient.ts @@ -347,7 +347,7 @@ export interface VerifiedPermissionsClientResolvedConfig extends VerifiedPermiss * control (ABAC) authorization models.
*For more information about configuring, administering, and using Amazon Verified Permissions in your * applications, see the Amazon Verified Permissions User Guide.
- *For more information about the Cedar policy language, see the Cedar Policy Language Guide.
+ *For more information about the Cedar policy language, see the Cedar Policy Language Guide.
*When you write Cedar policies that reference principals, resources and actions, * you can define the unique identifiers used for each of those elements. We strongly diff --git a/clients/client-verifiedpermissions/src/commands/CreateIdentitySourceCommand.ts b/clients/client-verifiedpermissions/src/commands/CreateIdentitySourceCommand.ts index 5e985fd594bd..bb8202d89b39 100644 --- a/clients/client-verifiedpermissions/src/commands/CreateIdentitySourceCommand.ts +++ b/clients/client-verifiedpermissions/src/commands/CreateIdentitySourceCommand.ts @@ -163,7 +163,7 @@ export interface CreateIdentitySourceCommandOutput extends CreateIdentitySourceO *
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
* *The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*For more information about configuring, administering, and using Amazon Verified Permissions in your * applications, see the Amazon Verified Permissions User Guide.
- *For more information about the Cedar policy language, see the Cedar Policy Language Guide.
+ *For more information about the Cedar policy language, see the Cedar Policy Language Guide.
*When you write Cedar policies that reference principals, resources and actions, * you can define the unique identifiers used for each of those elements. We strongly diff --git a/clients/client-verifiedpermissions/src/models/models_0.ts b/clients/client-verifiedpermissions/src/models/models_0.ts index 787cad9f72a9..8504fd3491cd 100644 --- a/clients/client-verifiedpermissions/src/models/models_0.ts +++ b/clients/client-verifiedpermissions/src/models/models_0.ts @@ -474,7 +474,7 @@ export interface ValidationExceptionField { *
*The policy attempts to access a record or entity attribute that isn't * specified in the schema. Test for the existence of the attribute first before - * attempting to access its value. For more information, see the has (presence of attribute test) operator in the + * attempting to access its value. For more information, see the has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*The policy attempts to access a record or entity attribute that is optional * and isn't guaranteed to be present. Test for the existence of the attribute * first before attempting to access its value. For more information, see the - * has (presence of attribute test) operator in the + * has (presence of attribute test) operator in the * Cedar Policy Language Guide.
*An attribute value of Boolean + *
An attribute value of Boolean * type.
*Example: \{"boolean": true\}
*
An attribute value of Long + *
An attribute value of Long * type.
*Example: \{"long": 0\}
*
An attribute value of String + *
An attribute value of String * type.
*Example: \{"string": "abc"\}
*
An attribute value of Set + *
An attribute value of Set * type.
*Example: \{"set": [ \{\} ] \}
*
An attribute value of Record + *
An attribute value of Record * type.
*Example: \{"record": \{ "keyName": \{\} \} \}
*
This data type is used as one of the fields in the EntitiesDefinition * structure.
*
- * \{
- * "id": \{
- * "entityType": "Photo",
- * "entityId": "VacationPhoto94.jpg"
- * \},
- * "Attributes": \{\},
- * "Parents": [
- * \{
- * "entityType": "Album",
- * "entityId": "alice_folder"
- * \}
- * ]
- * \}
+ * \{ "id": \{ "entityType": "Photo", "entityId": "VacationPhoto94.jpg" \},
+ * "Attributes": \{\}, "Parents": [ \{ "entityType": "Album", "entityId": "alice_folder" \}
+ * ] \}
*
An attribute value of Boolean\n type.
\nExample: {\"boolean\": true}\n
An attribute value of Boolean\n type.
\nExample: {\"boolean\": true}\n
An attribute value of Long\n type.
\nExample: {\"long\": 0}\n
An attribute value of Long\n type.
\nExample: {\"long\": 0}\n
An attribute value of String\n type.
\nExample: {\"string\": \"abc\"}\n
An attribute value of String\n type.
\nExample: {\"string\": \"abc\"}\n
An attribute value of Set\n type.
\nExample: {\"set\": [ {} ] }\n
An attribute value of Set\n type.
\nExample: {\"set\": [ {} ] }\n
An attribute value of Record\n type.
\nExample: {\"record\": { \"keyName\": {} } }\n
An attribute value of Record\n type.
\nExample: {\"record\": { \"keyName\": {} } }\n
Contains information about an entity that can be referenced in a Cedar\n policy.
\nThis data type is used as one of the fields in the EntitiesDefinition\n structure.
\n\n {\n \"id\": {\n \"entityType\": \"Photo\",\n \"entityId\": \"VacationPhoto94.jpg\"\n },\n \"Attributes\": {},\n \"Parents\": [\n {\n \"entityType\": \"Album\",\n \"entityId\": \"alice_folder\"\n }\n ]\n}\n
Contains information about an entity that can be referenced in a Cedar\n policy.
\nThis data type is used as one of the fields in the EntitiesDefinition\n structure.
\n\n { \"id\": { \"entityType\": \"Photo\", \"entityId\": \"VacationPhoto94.jpg\" },\n \"Attributes\": {}, \"Parents\": [ { \"entityType\": \"Album\", \"entityId\": \"alice_folder\" }\n ] }\n
The request failed because one or more input parameters don't satisfy their constraint\n requirements. The output is provided as a list of fields and a reason for each field that\n isn't valid.
\nThe possible reasons include the following:
\n\n UnrecognizedEntityType\n
\nThe policy includes an entity type that isn't found in the schema.
\n\n UnrecognizedActionId\n
\nThe policy includes an action id that isn't found in the schema.
\n\n InvalidActionApplication\n
\nThe policy includes an action that, according to the schema, doesn't support\n the specified principal and resource.
\n\n UnexpectedType\n
\nThe policy included an operand that isn't a valid type for the specified\n operation.
\n\n IncompatibleTypes\n
\nThe types of elements included in a set, or the types of\n expressions used in an if...then...else clause aren't compatible in\n this context.
\n MissingAttribute\n
\nThe policy attempts to access a record or entity attribute that isn't\n specified in the schema. Test for the existence of the attribute first before\n attempting to access its value. For more information, see the has (presence of attribute test) operator in the\n Cedar Policy Language Guide.
\n\n UnsafeOptionalAttributeAccess\n
\nThe policy attempts to access a record or entity attribute that is optional\n and isn't guaranteed to be present. Test for the existence of the attribute\n first before attempting to access its value. For more information, see the\n has (presence of attribute test) operator in the\n Cedar Policy Language Guide.
\n\n ImpossiblePolicy\n
\nCedar has determined that a policy condition always evaluates to false. If\n the policy is always false, it can never apply to any query, and so it can never\n affect an authorization decision.
\n\n WrongNumberArguments\n
\nThe policy references an extension type with the wrong number of\n arguments.
\n\n FunctionArgumentValidationError\n
\nCedar couldn't parse the argument passed to an extension type. For example,\n a string that is to be parsed as an IPv4 address can contain only digits and the\n period character.
\nThe request failed because one or more input parameters don't satisfy their constraint\n requirements. The output is provided as a list of fields and a reason for each field that\n isn't valid.
\nThe possible reasons include the following:
\n\n UnrecognizedEntityType\n
\nThe policy includes an entity type that isn't found in the schema.
\n\n UnrecognizedActionId\n
\nThe policy includes an action id that isn't found in the schema.
\n\n InvalidActionApplication\n
\nThe policy includes an action that, according to the schema, doesn't support\n the specified principal and resource.
\n\n UnexpectedType\n
\nThe policy included an operand that isn't a valid type for the specified\n operation.
\n\n IncompatibleTypes\n
\nThe types of elements included in a set, or the types of\n expressions used in an if...then...else clause aren't compatible in\n this context.
\n MissingAttribute\n
\nThe policy attempts to access a record or entity attribute that isn't\n specified in the schema. Test for the existence of the attribute first before\n attempting to access its value. For more information, see the has (presence of attribute test) operator in the\n Cedar Policy Language Guide.
\n\n UnsafeOptionalAttributeAccess\n
\nThe policy attempts to access a record or entity attribute that is optional\n and isn't guaranteed to be present. Test for the existence of the attribute\n first before attempting to access its value. For more information, see the\n has (presence of attribute test) operator in the\n Cedar Policy Language Guide.
\n\n ImpossiblePolicy\n
\nCedar has determined that a policy condition always evaluates to false. If\n the policy is always false, it can never apply to any query, and so it can never\n affect an authorization decision.
\n\n WrongNumberArguments\n
\nThe policy references an extension type with the wrong number of\n arguments.
\n\n FunctionArgumentValidationError\n
\nCedar couldn't parse the argument passed to an extension type. For example,\n a string that is to be parsed as an IPv4 address can contain only digits and the\n period character.
\nAmazon Verified Permissions is a permissions management service from Amazon Web Services. You can use Verified Permissions to manage\n permissions for your application, and authorize user access based on those permissions.\n Using Verified Permissions, application developers can grant access based on information about the\n users, resources, and requested actions. You can also evaluate additional information\n like group membership, attributes of the resources, and session context, such as time of\n request and IP addresses. Verified Permissions manages these permissions by letting you create and\n store authorization policies for your applications, such as consumer-facing web sites\n and enterprise business systems.
\nVerified Permissions uses Cedar as the policy language to express your permission requirements.\n Cedar supports both role-based access control (RBAC) and attribute-based access\n control (ABAC) authorization models.
\nFor more information about configuring, administering, and using Amazon Verified Permissions in your\n applications, see the Amazon Verified Permissions User Guide.
\nFor more information about the Cedar policy language, see the Cedar Policy Language Guide.
\nWhen you write Cedar policies that reference principals, resources and actions,\n you can define the unique identifiers used for each of those elements. We strongly\n recommend that you follow these best practices:
\n\n Use values like universally unique identifiers\n (UUIDs) for all principal and resource identifiers.\n
\nFor example, if user jane leaves the company, and you later\n let someone else use the name jane, then that new user\n automatically gets access to everything granted by policies that still\n reference User::\"jane\". Cedar can’t distinguish between the\n new user and the old. This applies to both principal and resource\n identifiers. Always use identifiers that are guaranteed unique and never\n reused to ensure that you don’t unintentionally grant access because of the\n presence of an old identifier in a policy.
Where you use a UUID for an entity, we recommend that you follow it with\n the // comment specifier and the ‘friendly’ name of your entity. This helps\n to make your policies easier to understand. For example: principal ==\n User::\"a1b2c3d4-e5f6-a1b2-c3d4-EXAMPLE11111\", // alice
\n\n Do not include personally identifying, confidential,\n or sensitive information as part of the unique identifier for your\n principals or resources. These identifiers are included in\n log entries shared in CloudTrail trails.
\nSeveral operations return structures that appear similar, but have different purposes.\n As new functionality is added to the product, the structure used in a parameter of one\n operation might need to change in a way that wouldn't make sense for the same parameter\n in a different operation. To help you understand the purpose of each, the following\n naming convention is used for the structures:
\nParameter type structures that end in Detail are used in\n Get operations.
Parameter type structures that end in Item are used in\n List operations.
Parameter type structures that use neither suffix are used in the mutating\n (create and update) operations.
\nAmazon Verified Permissions is a permissions management service from Amazon Web Services. You can use Verified Permissions to manage\n permissions for your application, and authorize user access based on those permissions.\n Using Verified Permissions, application developers can grant access based on information about the\n users, resources, and requested actions. You can also evaluate additional information\n like group membership, attributes of the resources, and session context, such as time of\n request and IP addresses. Verified Permissions manages these permissions by letting you create and\n store authorization policies for your applications, such as consumer-facing web sites\n and enterprise business systems.
\nVerified Permissions uses Cedar as the policy language to express your permission requirements.\n Cedar supports both role-based access control (RBAC) and attribute-based access\n control (ABAC) authorization models.
\nFor more information about configuring, administering, and using Amazon Verified Permissions in your\n applications, see the Amazon Verified Permissions User Guide.
\nFor more information about the Cedar policy language, see the Cedar Policy Language Guide.
\nWhen you write Cedar policies that reference principals, resources and actions,\n you can define the unique identifiers used for each of those elements. We strongly\n recommend that you follow these best practices:
\n\n Use values like universally unique identifiers\n (UUIDs) for all principal and resource identifiers.\n
\nFor example, if user jane leaves the company, and you later\n let someone else use the name jane, then that new user\n automatically gets access to everything granted by policies that still\n reference User::\"jane\". Cedar can’t distinguish between the\n new user and the old. This applies to both principal and resource\n identifiers. Always use identifiers that are guaranteed unique and never\n reused to ensure that you don’t unintentionally grant access because of the\n presence of an old identifier in a policy.
Where you use a UUID for an entity, we recommend that you follow it with\n the // comment specifier and the ‘friendly’ name of your entity. This helps\n to make your policies easier to understand. For example: principal ==\n User::\"a1b2c3d4-e5f6-a1b2-c3d4-EXAMPLE11111\", // alice
\n\n Do not include personally identifying, confidential,\n or sensitive information as part of the unique identifier for your\n principals or resources. These identifiers are included in\n log entries shared in CloudTrail trails.
\nSeveral operations return structures that appear similar, but have different purposes.\n As new functionality is added to the product, the structure used in a parameter of one\n operation might need to change in a way that wouldn't make sense for the same parameter\n in a different operation. To help you understand the purpose of each, the following\n naming convention is used for the structures:
\nParameter type structures that end in Detail are used in\n Get operations.
Parameter type structures that end in Item are used in\n List operations.
Parameter type structures that use neither suffix are used in the mutating\n (create and update) operations.
\n