BatchIsAuthorized

$result = $client->batchIsAuthorized([/* ... */]);
$promise = $client->batchIsAuthorizedAsync([/* ... */]);

Makes a series of decisions about multiple authorization requests for one principal or resource. Each request contains the equivalent content of an IsAuthorized request: principal, action, resource, and context. Either the principal or the resource parameter must be identical across all requests. For example, Verified Permissions won't evaluate a pair of requests where bob views photo1 and alice views photo2. Authorization of bob to view photo1 and photo2, or bob and alice to view photo1, are valid batches.

The request is evaluated against all policies in the specified policy store that match the entities that you declare. The result of the decisions is a series of Allow or Deny responses, along with the IDs of the policies that produced each decision.

The entities of a BatchIsAuthorized API request can contain up to 100 principals and up to 100 resources. The requests of a BatchIsAuthorized API request can contain up to 30 requests.

Parameter Syntax

$result = $client->batchIsAuthorized([
    'entities' => [
        'entityList' => [
            [
                'attributes' => [
                    '<String>' => [
                        'boolean' => true || false,
                        'entityIdentifier' => [
                            'entityId' => '<string>', // REQUIRED
                            'entityType' => '<string>', // REQUIRED
                        ],
                        'long' => <integer>,
                        'record' => [
                            '<String>' => [...], // RECURSIVE
                            // ...
                        ],
                        'set' => [
                            [...], // RECURSIVE
                            // ...
                        ],
                        'string' => '<string>',
                    ],
                    // ...
                ],
                'identifier' => [ // REQUIRED
                    'entityId' => '<string>', // REQUIRED
                    'entityType' => '<string>', // REQUIRED
                ],
                'parents' => [
                    [
                        'entityId' => '<string>', // REQUIRED
                        'entityType' => '<string>', // REQUIRED
                    ],
                    // ...
                ],
            ],
            // ...
        ],
    ],
    'policyStoreId' => '<string>', // REQUIRED
    'requests' => [ // REQUIRED
        [
            'action' => [
                'actionId' => '<string>', // REQUIRED
                'actionType' => '<string>', // REQUIRED
            ],
            'context' => [
                'contextMap' => [
                    '<String>' => [
                        'boolean' => true || false,
                        'entityIdentifier' => [
                            'entityId' => '<string>', // REQUIRED
                            'entityType' => '<string>', // REQUIRED
                        ],
                        'long' => <integer>,
                        'record' => [
                            '<String>' => [...], // RECURSIVE
                            // ...
                        ],
                        'set' => [
                            [...], // RECURSIVE
                            // ...
                        ],
                        'string' => '<string>',
                    ],
                    // ...
                ],
            ],
            'principal' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
            'resource' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
        ],
        // ...
    ],
]);

Parameter Details

Result Syntax

[
    'results' => [
        [
            'decision' => 'ALLOW|DENY',
            'determiningPolicies' => [
                [
                    'policyId' => '<string>',
                ],
                // ...
            ],
            'errors' => [
                [
                    'errorDescription' => '<string>',
                ],
                // ...
            ],
            'request' => [
                'action' => [
                    'actionId' => '<string>',
                    'actionType' => '<string>',
                ],
                'context' => [
                    'contextMap' => [
                        '<String>' => [
                            'boolean' => true || false,
                            'entityIdentifier' => [
                                'entityId' => '<string>',
                                'entityType' => '<string>',
                            ],
                            'long' => <integer>,
                            'record' => [
                                '<String>' => [...], // RECURSIVE
                                // ...
                            ],
                            'set' => [
                                [...], // RECURSIVE
                                // ...
                            ],
                            'string' => '<string>',
                        ],
                        // ...
                    ],
                ],
                'principal' => [
                    'entityId' => '<string>',
                    'entityType' => '<string>',
                ],
                'resource' => [
                    'entityId' => '<string>',
                    'entityType' => '<string>',
                ],
            ],
        ],
        // ...
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

BatchIsAuthorizedWithToken

$result = $client->batchIsAuthorizedWithToken([/* ... */]);
$promise = $client->batchIsAuthorizedWithTokenAsync([/* ... */]);

Makes a series of decisions about multiple authorization requests for one token. The principal in this request comes from an external identity source in the form of an identity or access token, formatted as a JSON web token (JWT). The information in the parameters can also define additional context that Verified Permissions can include in the evaluations.

The request is evaluated against all policies in the specified policy store that match the entities that you provide in the entities declaration and in the token. The result of the decisions is a series of Allow or Deny responses, along with the IDs of the policies that produced each decision.

The entities of a BatchIsAuthorizedWithToken API request can contain up to 100 resources and up to 99 user groups. The requests of a BatchIsAuthorizedWithToken API request can contain up to 30 requests.

Parameter Syntax

$result = $client->batchIsAuthorizedWithToken([
    'accessToken' => '<string>',
    'entities' => [
        'entityList' => [
            [
                'attributes' => [
                    '<String>' => [
                        'boolean' => true || false,
                        'entityIdentifier' => [
                            'entityId' => '<string>', // REQUIRED
                            'entityType' => '<string>', // REQUIRED
                        ],
                        'long' => <integer>,
                        'record' => [
                            '<String>' => [...], // RECURSIVE
                            // ...
                        ],
                        'set' => [
                            [...], // RECURSIVE
                            // ...
                        ],
                        'string' => '<string>',
                    ],
                    // ...
                ],
                'identifier' => [ // REQUIRED
                    'entityId' => '<string>', // REQUIRED
                    'entityType' => '<string>', // REQUIRED
                ],
                'parents' => [
                    [
                        'entityId' => '<string>', // REQUIRED
                        'entityType' => '<string>', // REQUIRED
                    ],
                    // ...
                ],
            ],
            // ...
        ],
    ],
    'identityToken' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
    'requests' => [ // REQUIRED
        [
            'action' => [
                'actionId' => '<string>', // REQUIRED
                'actionType' => '<string>', // REQUIRED
            ],
            'context' => [
                'contextMap' => [
                    '<String>' => [
                        'boolean' => true || false,
                        'entityIdentifier' => [
                            'entityId' => '<string>', // REQUIRED
                            'entityType' => '<string>', // REQUIRED
                        ],
                        'long' => <integer>,
                        'record' => [
                            '<String>' => [...], // RECURSIVE
                            // ...
                        ],
                        'set' => [
                            [...], // RECURSIVE
                            // ...
                        ],
                        'string' => '<string>',
                    ],
                    // ...
                ],
            ],
            'resource' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
        ],
        // ...
    ],
]);

Parameter Details

Result Syntax

[
    'principal' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
    'results' => [
        [
            'decision' => 'ALLOW|DENY',
            'determiningPolicies' => [
                [
                    'policyId' => '<string>',
                ],
                // ...
            ],
            'errors' => [
                [
                    'errorDescription' => '<string>',
                ],
                // ...
            ],
            'request' => [
                'action' => [
                    'actionId' => '<string>',
                    'actionType' => '<string>',
                ],
                'context' => [
                    'contextMap' => [
                        '<String>' => [
                            'boolean' => true || false,
                            'entityIdentifier' => [
                                'entityId' => '<string>',
                                'entityType' => '<string>',
                            ],
                            'long' => <integer>,
                            'record' => [
                                '<String>' => [...], // RECURSIVE
                                // ...
                            ],
                            'set' => [
                                [...], // RECURSIVE
                                // ...
                            ],
                            'string' => '<string>',
                        ],
                        // ...
                    ],
                ],
                'resource' => [
                    'entityId' => '<string>',
                    'entityType' => '<string>',
                ],
            ],
        ],
        // ...
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

CreateIdentitySource

$result = $client->createIdentitySource([/* ... */]);
$promise = $client->createIdentitySourceAsync([/* ... */]);

Adds an identity source to a policy store–an Amazon Cognito user pool or OpenID Connect (OIDC) identity provider (IdP).

After you create an identity source, you can use the identities provided by the IdP as proxies for the principal in authorization queries that use the IsAuthorizedWithToken or BatchIsAuthorizedWithToken API operations. These identities take the form of tokens that contain claims about the user, such as IDs, attributes and group memberships. Identity sources provide identity (ID) tokens and access tokens. Verified Permissions derives information about your user and session from token claims. Access tokens provide action context to your policies, and ID tokens provide principal Attributes.

Parameter Syntax

$result = $client->createIdentitySource([
    'clientToken' => '<string>',
    'configuration' => [ // REQUIRED
        'cognitoUserPoolConfiguration' => [
            'clientIds' => ['<string>', ...],
            'groupConfiguration' => [
                'groupEntityType' => '<string>', // REQUIRED
            ],
            'userPoolArn' => '<string>', // REQUIRED
        ],
        'openIdConnectConfiguration' => [
            'entityIdPrefix' => '<string>',
            'groupConfiguration' => [
                'groupClaim' => '<string>', // REQUIRED
                'groupEntityType' => '<string>', // REQUIRED
            ],
            'issuer' => '<string>', // REQUIRED
            'tokenSelection' => [ // REQUIRED
                'accessTokenOnly' => [
                    'audiences' => ['<string>', ...],
                    'principalIdClaim' => '<string>',
                ],
                'identityTokenOnly' => [
                    'clientIds' => ['<string>', ...],
                    'principalIdClaim' => '<string>',
                ],
            ],
        ],
    ],
    'policyStoreId' => '<string>', // REQUIRED
    'principalEntityType' => '<string>',
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'identitySourceId' => '<string>',
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ServiceQuotaExceededException:

The request failed because it would cause a service quota to be exceeded.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

CreatePolicy

$result = $client->createPolicy([/* ... */]);
$promise = $client->createPolicyAsync([/* ... */]);

Creates a Cedar policy and saves it in the specified policy store. You can create either a static policy or a policy linked to a policy template.

• To create a static policy, provide the Cedar policy text in the StaticPolicy section of the PolicyDefinition.

• To create a policy that is dynamically linked to a policy template, specify the policy template ID and the principal and resource to associate with this policy in the templateLinked section of the PolicyDefinition. If the policy template is ever updated, any policies linked to the policy template automatically use the updated template.

Parameter Syntax

$result = $client->createPolicy([
    'clientToken' => '<string>',
    'definition' => [ // REQUIRED
        'static' => [
            'description' => '<string>',
            'statement' => '<string>', // REQUIRED
        ],
        'templateLinked' => [
            'policyTemplateId' => '<string>', // REQUIRED
            'principal' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
            'resource' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
        ],
    ],
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'actions' => [
        [
            'actionId' => '<string>',
            'actionType' => '<string>',
        ],
        // ...
    ],
    'createdDate' => <DateTime>,
    'effect' => 'Permit|Forbid',
    'lastUpdatedDate' => <DateTime>,
    'policyId' => '<string>',
    'policyStoreId' => '<string>',
    'policyType' => 'STATIC|TEMPLATE_LINKED',
    'principal' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
    'resource' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ServiceQuotaExceededException:

The request failed because it would cause a service quota to be exceeded.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

CreatePolicyStore

$result = $client->createPolicyStore([/* ... */]);
$promise = $client->createPolicyStoreAsync([/* ... */]);

Creates a policy store. A policy store is a container for policy resources.

Parameter Syntax

$result = $client->createPolicyStore([
    'clientToken' => '<string>',
    'description' => '<string>',
    'validationSettings' => [ // REQUIRED
        'mode' => 'OFF|STRICT', // REQUIRED
    ],
]);

Parameter Details

Result Syntax

[
    'arn' => '<string>',
    'createdDate' => <DateTime>,
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ServiceQuotaExceededException:

The request failed because it would cause a service quota to be exceeded.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

CreatePolicyTemplate

$result = $client->createPolicyTemplate([/* ... */]);
$promise = $client->createPolicyTemplateAsync([/* ... */]);

Creates a policy template. A template can use placeholders for the principal and resource. A template must be instantiated into a policy by associating it with specific principals and resources to use for the placeholders. That instantiated policy can then be considered in authorization decisions. The instantiated policy works identically to any other policy, except that it is dynamically linked to the template. If the template changes, then any policies that are linked to that template are immediately updated as well.

Parameter Syntax

$result = $client->createPolicyTemplate([
    'clientToken' => '<string>',
    'description' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
    'statement' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
    'policyTemplateId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ServiceQuotaExceededException:

The request failed because it would cause a service quota to be exceeded.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

DeleteIdentitySource

$result = $client->deleteIdentitySource([/* ... */]);
$promise = $client->deleteIdentitySourceAsync([/* ... */]);

Deletes an identity source that references an identity provider (IdP) such as Amazon Cognito. After you delete the identity source, you can no longer use tokens for identities from that identity source to represent principals in authorization queries made using IsAuthorizedWithToken. operations.

Parameter Syntax

$result = $client->deleteIdentitySource([
    'identitySourceId' => '<string>', // REQUIRED
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

DeletePolicy

$result = $client->deletePolicy([/* ... */]);
$promise = $client->deletePolicyAsync([/* ... */]);

Deletes the specified policy from the policy store.

This operation is idempotent; if you specify a policy that doesn't exist, the request response returns a successful HTTP 200 status code.

Parameter Syntax

$result = $client->deletePolicy([
    'policyId' => '<string>', // REQUIRED
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

DeletePolicyStore

$result = $client->deletePolicyStore([/* ... */]);
$promise = $client->deletePolicyStoreAsync([/* ... */]);

Deletes the specified policy store.

This operation is idempotent. If you specify a policy store that does not exist, the request response will still return a successful HTTP 200 status code.

Parameter Syntax

$result = $client->deletePolicyStore([
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

DeletePolicyTemplate

$result = $client->deletePolicyTemplate([/* ... */]);
$promise = $client->deletePolicyTemplateAsync([/* ... */]);

Deletes the specified policy template from the policy store.

Parameter Syntax

$result = $client->deletePolicyTemplate([
    'policyStoreId' => '<string>', // REQUIRED
    'policyTemplateId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

GetIdentitySource

$result = $client->getIdentitySource([/* ... */]);
$promise = $client->getIdentitySourceAsync([/* ... */]);

Retrieves the details about the specified identity source.

Parameter Syntax

$result = $client->getIdentitySource([
    'identitySourceId' => '<string>', // REQUIRED
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'configuration' => [
        'cognitoUserPoolConfiguration' => [
            'clientIds' => ['<string>', ...],
            'groupConfiguration' => [
                'groupEntityType' => '<string>',
            ],
            'issuer' => '<string>',
            'userPoolArn' => '<string>',
        ],
        'openIdConnectConfiguration' => [
            'entityIdPrefix' => '<string>',
            'groupConfiguration' => [
                'groupClaim' => '<string>',
                'groupEntityType' => '<string>',
            ],
            'issuer' => '<string>',
            'tokenSelection' => [
                'accessTokenOnly' => [
                    'audiences' => ['<string>', ...],
                    'principalIdClaim' => '<string>',
                ],
                'identityTokenOnly' => [
                    'clientIds' => ['<string>', ...],
                    'principalIdClaim' => '<string>',
                ],
            ],
        ],
    ],
    'createdDate' => <DateTime>,
    'details' => [
        'clientIds' => ['<string>', ...],
        'discoveryUrl' => '<string>',
        'openIdIssuer' => 'COGNITO',
        'userPoolArn' => '<string>',
    ],
    'identitySourceId' => '<string>',
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
    'principalEntityType' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

GetPolicy

$result = $client->getPolicy([/* ... */]);
$promise = $client->getPolicyAsync([/* ... */]);

Retrieves information about the specified policy.

Parameter Syntax

$result = $client->getPolicy([
    'policyId' => '<string>', // REQUIRED
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'actions' => [
        [
            'actionId' => '<string>',
            'actionType' => '<string>',
        ],
        // ...
    ],
    'createdDate' => <DateTime>,
    'definition' => [
        'static' => [
            'description' => '<string>',
            'statement' => '<string>',
        ],
        'templateLinked' => [
            'policyTemplateId' => '<string>',
            'principal' => [
                'entityId' => '<string>',
                'entityType' => '<string>',
            ],
            'resource' => [
                'entityId' => '<string>',
                'entityType' => '<string>',
            ],
        ],
    ],
    'effect' => 'Permit|Forbid',
    'lastUpdatedDate' => <DateTime>,
    'policyId' => '<string>',
    'policyStoreId' => '<string>',
    'policyType' => 'STATIC|TEMPLATE_LINKED',
    'principal' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
    'resource' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

GetPolicyStore

$result = $client->getPolicyStore([/* ... */]);
$promise = $client->getPolicyStoreAsync([/* ... */]);

Retrieves details about a policy store.

Parameter Syntax

$result = $client->getPolicyStore([
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'arn' => '<string>',
    'createdDate' => <DateTime>,
    'description' => '<string>',
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
    'validationSettings' => [
        'mode' => 'OFF|STRICT',
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

GetPolicyTemplate

$result = $client->getPolicyTemplate([/* ... */]);
$promise = $client->getPolicyTemplateAsync([/* ... */]);

Retrieve the details for the specified policy template in the specified policy store.

Parameter Syntax

$result = $client->getPolicyTemplate([
    'policyStoreId' => '<string>', // REQUIRED
    'policyTemplateId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'description' => '<string>',
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
    'policyTemplateId' => '<string>',
    'statement' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

GetSchema

$result = $client->getSchema([/* ... */]);
$promise = $client->getSchemaAsync([/* ... */]);

Retrieve the details for the specified schema in the specified policy store.

Parameter Syntax

$result = $client->getSchema([
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'lastUpdatedDate' => <DateTime>,
    'namespaces' => ['<string>', ...],
    'policyStoreId' => '<string>',
    'schema' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

IsAuthorized

$result = $client->isAuthorized([/* ... */]);
$promise = $client->isAuthorizedAsync([/* ... */]);

Makes an authorization decision about a service request described in the parameters. The information in the parameters can also define additional context that Verified Permissions can include in the evaluation. The request is evaluated against all matching policies in the specified policy store. The result of the decision is either Allow or Deny, along with a list of the policies that resulted in the decision.

Parameter Syntax

$result = $client->isAuthorized([
    'action' => [
        'actionId' => '<string>', // REQUIRED
        'actionType' => '<string>', // REQUIRED
    ],
    'context' => [
        'contextMap' => [
            '<String>' => [
                'boolean' => true || false,
                'entityIdentifier' => [
                    'entityId' => '<string>', // REQUIRED
                    'entityType' => '<string>', // REQUIRED
                ],
                'long' => <integer>,
                'record' => [
                    '<String>' => [...], // RECURSIVE
                    // ...
                ],
                'set' => [
                    [...], // RECURSIVE
                    // ...
                ],
                'string' => '<string>',
            ],
            // ...
        ],
    ],
    'entities' => [
        'entityList' => [
            [
                'attributes' => [
                    '<String>' => [
                        'boolean' => true || false,
                        'entityIdentifier' => [
                            'entityId' => '<string>', // REQUIRED
                            'entityType' => '<string>', // REQUIRED
                        ],
                        'long' => <integer>,
                        'record' => [
                            '<String>' => [...], // RECURSIVE
                            // ...
                        ],
                        'set' => [
                            [...], // RECURSIVE
                            // ...
                        ],
                        'string' => '<string>',
                    ],
                    // ...
                ],
                'identifier' => [ // REQUIRED
                    'entityId' => '<string>', // REQUIRED
                    'entityType' => '<string>', // REQUIRED
                ],
                'parents' => [
                    [
                        'entityId' => '<string>', // REQUIRED
                        'entityType' => '<string>', // REQUIRED
                    ],
                    // ...
                ],
            ],
            // ...
        ],
    ],
    'policyStoreId' => '<string>', // REQUIRED
    'principal' => [
        'entityId' => '<string>', // REQUIRED
        'entityType' => '<string>', // REQUIRED
    ],
    'resource' => [
        'entityId' => '<string>', // REQUIRED
        'entityType' => '<string>', // REQUIRED
    ],
]);

Parameter Details

Result Syntax

[
    'decision' => 'ALLOW|DENY',
    'determiningPolicies' => [
        [
            'policyId' => '<string>',
        ],
        // ...
    ],
    'errors' => [
        [
            'errorDescription' => '<string>',
        ],
        // ...
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

IsAuthorizedWithToken

$result = $client->isAuthorizedWithToken([/* ... */]);
$promise = $client->isAuthorizedWithTokenAsync([/* ... */]);

Makes an authorization decision about a service request described in the parameters. The principal in this request comes from an external identity source in the form of an identity token formatted as a JSON web token (JWT). The information in the parameters can also define additional context that Verified Permissions can include in the evaluation. The request is evaluated against all matching policies in the specified policy store. The result of the decision is either Allow or Deny, along with a list of the policies that resulted in the decision.

At this time, Verified Permissions accepts tokens from only Amazon Cognito.

Verified Permissions validates each token that is specified in a request by checking its expiration date and its signature.

Parameter Syntax

$result = $client->isAuthorizedWithToken([
    'accessToken' => '<string>',
    'action' => [
        'actionId' => '<string>', // REQUIRED
        'actionType' => '<string>', // REQUIRED
    ],
    'context' => [
        'contextMap' => [
            '<String>' => [
                'boolean' => true || false,
                'entityIdentifier' => [
                    'entityId' => '<string>', // REQUIRED
                    'entityType' => '<string>', // REQUIRED
                ],
                'long' => <integer>,
                'record' => [
                    '<String>' => [...], // RECURSIVE
                    // ...
                ],
                'set' => [
                    [...], // RECURSIVE
                    // ...
                ],
                'string' => '<string>',
            ],
            // ...
        ],
    ],
    'entities' => [
        'entityList' => [
            [
                'attributes' => [
                    '<String>' => [
                        'boolean' => true || false,
                        'entityIdentifier' => [
                            'entityId' => '<string>', // REQUIRED
                            'entityType' => '<string>', // REQUIRED
                        ],
                        'long' => <integer>,
                        'record' => [
                            '<String>' => [...], // RECURSIVE
                            // ...
                        ],
                        'set' => [
                            [...], // RECURSIVE
                            // ...
                        ],
                        'string' => '<string>',
                    ],
                    // ...
                ],
                'identifier' => [ // REQUIRED
                    'entityId' => '<string>', // REQUIRED
                    'entityType' => '<string>', // REQUIRED
                ],
                'parents' => [
                    [
                        'entityId' => '<string>', // REQUIRED
                        'entityType' => '<string>', // REQUIRED
                    ],
                    // ...
                ],
            ],
            // ...
        ],
    ],
    'identityToken' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
    'resource' => [
        'entityId' => '<string>', // REQUIRED
        'entityType' => '<string>', // REQUIRED
    ],
]);

Parameter Details

Result Syntax

[
    'decision' => 'ALLOW|DENY',
    'determiningPolicies' => [
        [
            'policyId' => '<string>',
        ],
        // ...
    ],
    'errors' => [
        [
            'errorDescription' => '<string>',
        ],
        // ...
    ],
    'principal' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

ListIdentitySources

$result = $client->listIdentitySources([/* ... */]);
$promise = $client->listIdentitySourcesAsync([/* ... */]);

Returns a paginated list of all of the identity sources defined in the specified policy store.

Parameter Syntax

$result = $client->listIdentitySources([
    'filters' => [
        [
            'principalEntityType' => '<string>',
        ],
        // ...
    ],
    'maxResults' => <integer>,
    'nextToken' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'identitySources' => [
        [
            'configuration' => [
                'cognitoUserPoolConfiguration' => [
                    'clientIds' => ['<string>', ...],
                    'groupConfiguration' => [
                        'groupEntityType' => '<string>',
                    ],
                    'issuer' => '<string>',
                    'userPoolArn' => '<string>',
                ],
                'openIdConnectConfiguration' => [
                    'entityIdPrefix' => '<string>',
                    'groupConfiguration' => [
                        'groupClaim' => '<string>',
                        'groupEntityType' => '<string>',
                    ],
                    'issuer' => '<string>',
                    'tokenSelection' => [
                        'accessTokenOnly' => [
                            'audiences' => ['<string>', ...],
                            'principalIdClaim' => '<string>',
                        ],
                        'identityTokenOnly' => [
                            'clientIds' => ['<string>', ...],
                            'principalIdClaim' => '<string>',
                        ],
                    ],
                ],
            ],
            'createdDate' => <DateTime>,
            'details' => [
                'clientIds' => ['<string>', ...],
                'discoveryUrl' => '<string>',
                'openIdIssuer' => 'COGNITO',
                'userPoolArn' => '<string>',
            ],
            'identitySourceId' => '<string>',
            'lastUpdatedDate' => <DateTime>,
            'policyStoreId' => '<string>',
            'principalEntityType' => '<string>',
        ],
        // ...
    ],
    'nextToken' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

ListPolicies

$result = $client->listPolicies([/* ... */]);
$promise = $client->listPoliciesAsync([/* ... */]);

Returns a paginated list of all policies stored in the specified policy store.

Parameter Syntax

$result = $client->listPolicies([
    'filter' => [
        'policyTemplateId' => '<string>',
        'policyType' => 'STATIC|TEMPLATE_LINKED',
        'principal' => [
            'identifier' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
            'unspecified' => true || false,
        ],
        'resource' => [
            'identifier' => [
                'entityId' => '<string>', // REQUIRED
                'entityType' => '<string>', // REQUIRED
            ],
            'unspecified' => true || false,
        ],
    ],
    'maxResults' => <integer>,
    'nextToken' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'nextToken' => '<string>',
    'policies' => [
        [
            'actions' => [
                [
                    'actionId' => '<string>',
                    'actionType' => '<string>',
                ],
                // ...
            ],
            'createdDate' => <DateTime>,
            'definition' => [
                'static' => [
                    'description' => '<string>',
                ],
                'templateLinked' => [
                    'policyTemplateId' => '<string>',
                    'principal' => [
                        'entityId' => '<string>',
                        'entityType' => '<string>',
                    ],
                    'resource' => [
                        'entityId' => '<string>',
                        'entityType' => '<string>',
                    ],
                ],
            ],
            'effect' => 'Permit|Forbid',
            'lastUpdatedDate' => <DateTime>,
            'policyId' => '<string>',
            'policyStoreId' => '<string>',
            'policyType' => 'STATIC|TEMPLATE_LINKED',
            'principal' => [
                'entityId' => '<string>',
                'entityType' => '<string>',
            ],
            'resource' => [
                'entityId' => '<string>',
                'entityType' => '<string>',
            ],
        ],
        // ...
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

ListPolicyStores

$result = $client->listPolicyStores([/* ... */]);
$promise = $client->listPolicyStoresAsync([/* ... */]);

Returns a paginated list of all policy stores in the calling Amazon Web Services account.

Parameter Syntax

$result = $client->listPolicyStores([
    'maxResults' => <integer>,
    'nextToken' => '<string>',
]);

Parameter Details

Result Syntax

[
    'nextToken' => '<string>',
    'policyStores' => [
        [
            'arn' => '<string>',
            'createdDate' => <DateTime>,
            'description' => '<string>',
            'lastUpdatedDate' => <DateTime>,
            'policyStoreId' => '<string>',
        ],
        // ...
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

ListPolicyTemplates

$result = $client->listPolicyTemplates([/* ... */]);
$promise = $client->listPolicyTemplatesAsync([/* ... */]);

Returns a paginated list of all policy templates in the specified policy store.

Parameter Syntax

$result = $client->listPolicyTemplates([
    'maxResults' => <integer>,
    'nextToken' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'nextToken' => '<string>',
    'policyTemplates' => [
        [
            'createdDate' => <DateTime>,
            'description' => '<string>',
            'lastUpdatedDate' => <DateTime>,
            'policyStoreId' => '<string>',
            'policyTemplateId' => '<string>',
        ],
        // ...
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

PutSchema

$result = $client->putSchema([/* ... */]);
$promise = $client->putSchemaAsync([/* ... */]);

Creates or updates the policy schema in the specified policy store. The schema is used to validate any Cedar policies and policy templates submitted to the policy store. Any changes to the schema validate only policies and templates submitted after the schema change. Existing policies and templates are not re-evaluated against the changed schema. If you later update a policy, then it is evaluated against the new schema at that time.

Parameter Syntax

$result = $client->putSchema([
    'definition' => [ // REQUIRED
        'cedarJson' => '<string>',
    ],
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'lastUpdatedDate' => <DateTime>,
    'namespaces' => ['<string>', ...],
    'policyStoreId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ServiceQuotaExceededException:

The request failed because it would cause a service quota to be exceeded.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

UpdateIdentitySource

$result = $client->updateIdentitySource([/* ... */]);
$promise = $client->updateIdentitySourceAsync([/* ... */]);

Updates the specified identity source to use a new identity provider (IdP), or to change the mapping of identities from the IdP to a different principal entity type.

Parameter Syntax

$result = $client->updateIdentitySource([
    'identitySourceId' => '<string>', // REQUIRED
    'policyStoreId' => '<string>', // REQUIRED
    'principalEntityType' => '<string>',
    'updateConfiguration' => [ // REQUIRED
        'cognitoUserPoolConfiguration' => [
            'clientIds' => ['<string>', ...],
            'groupConfiguration' => [
                'groupEntityType' => '<string>', // REQUIRED
            ],
            'userPoolArn' => '<string>', // REQUIRED
        ],
        'openIdConnectConfiguration' => [
            'entityIdPrefix' => '<string>',
            'groupConfiguration' => [
                'groupClaim' => '<string>', // REQUIRED
                'groupEntityType' => '<string>', // REQUIRED
            ],
            'issuer' => '<string>', // REQUIRED
            'tokenSelection' => [ // REQUIRED
                'accessTokenOnly' => [
                    'audiences' => ['<string>', ...],
                    'principalIdClaim' => '<string>',
                ],
                'identityTokenOnly' => [
                    'clientIds' => ['<string>', ...],
                    'principalIdClaim' => '<string>',
                ],
            ],
        ],
    ],
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'identitySourceId' => '<string>',
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

UpdatePolicy

$result = $client->updatePolicy([/* ... */]);
$promise = $client->updatePolicyAsync([/* ... */]);

Modifies a Cedar static policy in the specified policy store. You can change only certain elements of the UpdatePolicyDefinition parameter. You can directly update only static policies. To change a template-linked policy, you must update the template instead, using UpdatePolicyTemplate.

Parameter Syntax

$result = $client->updatePolicy([
    'definition' => [ // REQUIRED
        'static' => [
            'description' => '<string>',
            'statement' => '<string>', // REQUIRED
        ],
    ],
    'policyId' => '<string>', // REQUIRED
    'policyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'actions' => [
        [
            'actionId' => '<string>',
            'actionType' => '<string>',
        ],
        // ...
    ],
    'createdDate' => <DateTime>,
    'effect' => 'Permit|Forbid',
    'lastUpdatedDate' => <DateTime>,
    'policyId' => '<string>',
    'policyStoreId' => '<string>',
    'policyType' => 'STATIC|TEMPLATE_LINKED',
    'principal' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
    'resource' => [
        'entityId' => '<string>',
        'entityType' => '<string>',
    ],
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ServiceQuotaExceededException:

The request failed because it would cause a service quota to be exceeded.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

UpdatePolicyStore

$result = $client->updatePolicyStore([/* ... */]);
$promise = $client->updatePolicyStoreAsync([/* ... */]);

Modifies the validation setting for a policy store.

Parameter Syntax

$result = $client->updatePolicyStore([
    'description' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
    'validationSettings' => [ // REQUIRED
        'mode' => 'OFF|STRICT', // REQUIRED
    ],
]);

Parameter Details

Result Syntax

[
    'arn' => '<string>',
    'createdDate' => <DateTime>,
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later

UpdatePolicyTemplate

$result = $client->updatePolicyTemplate([/* ... */]);
$promise = $client->updatePolicyTemplateAsync([/* ... */]);

Updates the specified policy template. You can update only the description and the some elements of the policyBody.

Parameter Syntax

$result = $client->updatePolicyTemplate([
    'description' => '<string>',
    'policyStoreId' => '<string>', // REQUIRED
    'policyTemplateId' => '<string>', // REQUIRED
    'statement' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'createdDate' => <DateTime>,
    'lastUpdatedDate' => <DateTime>,
    'policyStoreId' => '<string>',
    'policyTemplateId' => '<string>',
]

Result Details

Errors

ValidationException:

The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.

The possible reasons include the following:

• UnrecognizedEntityType

  The policy includes an entity type that isn't found in the schema.

• UnrecognizedActionId

  The policy includes an action id that isn't found in the schema.

• InvalidActionApplication

  The policy includes an action that, according to the schema, doesn't support the specified principal and resource.

• UnexpectedType

  The policy included an operand that isn't a valid type for the specified operation.

• IncompatibleTypes

  The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context.

• MissingAttribute

  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 Cedar Policy Language Guide.

• UnsafeOptionalAttributeAccess

  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 Cedar Policy Language Guide.

• ImpossiblePolicy

  Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.

• WrongNumberArguments

  The policy references an extension type with the wrong number of arguments.

• FunctionArgumentValidationError

  Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.

ConflictException:

The request failed because another request to modify a resource occurred at the same.

AccessDeniedException:

You don't have sufficient access to perform this action.

ResourceNotFoundException:

The request failed because it references a resource that doesn't exist.

ThrottlingException:

The request failed because it exceeded a throttling quota.

InternalServerException:

The request failed because of an internal error. Try your request again later