@Generated(value="software.amazon.awssdk:codegen") @ThreadSafe public interface VerifiedPermissionsClient extends AwsClient
builder()
method.
Amazon Verified Permissions is a permissions management service from Amazon Web Services. You can use Verified Permissions to manage permissions for your application, and authorize user access based on those permissions. Using Verified Permissions, application developers can grant access based on information about the users, resources, and requested actions. You can also evaluate additional information like group membership, attributes of the resources, and session context, such as time of request and IP addresses. Verified Permissions manages these permissions by letting you create and store authorization policies for your applications, such as consumer-facing web sites and enterprise business systems.
Verified Permissions uses Cedar as the policy language to express your permission requirements. Cedar supports both role-based access control (RBAC) and attribute-based access control (ABAC) authorization models.
For more information about configuring, administering, and using Amazon Verified Permissions in your applications, see the Amazon Verified Permissions User Guide.
For more information about the Cedar policy language, see the Cedar Policy Language Guide.
When you write Cedar policies that reference principals, resources and actions, you can define the unique identifiers used for each of those elements. We strongly recommend that you follow these best practices:
Use values like universally unique identifiers (UUIDs) for all principal and resource identifiers.
For example, if user jane leaves the company, and you later let someone else use the name
jane, then that new user automatically gets access to everything granted by policies that still
reference User::"jane". Cedar can’t distinguish between the new user and the old. This applies to both
principal and resource identifiers. Always use identifiers that are guaranteed unique and never reused to ensure that
you don’t unintentionally grant access because of the presence of an old identifier in a policy.
Where you use a UUID for an entity, we recommend that you follow it with the // comment specifier and the ‘friendly’ name of your entity. This helps to make your policies easier to understand. For example: principal == User::"a1b2c3d4-e5f6-a1b2-c3d4-EXAMPLE11111", // alice
Do not include personally identifying, confidential, or sensitive information as part of the unique identifier for your principals or resources. These identifiers are included in log entries shared in CloudTrail trails.
Several operations return structures that appear similar, but have different purposes. As new functionality is added to the product, the structure used in a parameter of one operation might need to change in a way that wouldn't make sense for the same parameter in a different operation. To help you understand the purpose of each, the following naming convention is used for the structures:
Parameters that end in Detail are used in Get operations.
Parameters that end in Item are used in List operations.
Parameters that use neither suffix are used in the mutating (create and update) operations.
| Modifier and Type | Field and Description |
|---|---|
static String |
SERVICE_METADATA_ID
Value for looking up the service's metadata from the
ServiceMetadataProvider. |
static String |
SERVICE_NAME |
| Modifier and Type | Method and Description |
|---|---|
static VerifiedPermissionsClientBuilder |
builder()
Create a builder that can be used to configure and create a
VerifiedPermissionsClient. |
static VerifiedPermissionsClient |
create()
Create a
VerifiedPermissionsClient with the region loaded from the
DefaultAwsRegionProviderChain and credentials loaded from the
DefaultCredentialsProvider. |
default CreateIdentitySourceResponse |
createIdentitySource(Consumer<CreateIdentitySourceRequest.Builder> createIdentitySourceRequest)
Creates a reference to an Amazon Cognito user pool as an external identity provider (IdP).
|
default CreateIdentitySourceResponse |
createIdentitySource(CreateIdentitySourceRequest createIdentitySourceRequest)
Creates a reference to an Amazon Cognito user pool as an external identity provider (IdP).
|
default CreatePolicyResponse |
createPolicy(Consumer<CreatePolicyRequest.Builder> createPolicyRequest)
Creates a Cedar policy and saves it in the specified policy store.
|
default CreatePolicyResponse |
createPolicy(CreatePolicyRequest createPolicyRequest)
Creates a Cedar policy and saves it in the specified policy store.
|
default CreatePolicyStoreResponse |
createPolicyStore(Consumer<CreatePolicyStoreRequest.Builder> createPolicyStoreRequest)
Creates a policy store.
|
default CreatePolicyStoreResponse |
createPolicyStore(CreatePolicyStoreRequest createPolicyStoreRequest)
Creates a policy store.
|
default CreatePolicyTemplateResponse |
createPolicyTemplate(Consumer<CreatePolicyTemplateRequest.Builder> createPolicyTemplateRequest)
Creates a policy template.
|
default CreatePolicyTemplateResponse |
createPolicyTemplate(CreatePolicyTemplateRequest createPolicyTemplateRequest)
Creates a policy template.
|
default DeleteIdentitySourceResponse |
deleteIdentitySource(Consumer<DeleteIdentitySourceRequest.Builder> deleteIdentitySourceRequest)
Deletes an identity source that references an identity provider (IdP) such as Amazon Cognito.
|
default DeleteIdentitySourceResponse |
deleteIdentitySource(DeleteIdentitySourceRequest deleteIdentitySourceRequest)
Deletes an identity source that references an identity provider (IdP) such as Amazon Cognito.
|
default DeletePolicyResponse |
deletePolicy(Consumer<DeletePolicyRequest.Builder> deletePolicyRequest)
Deletes the specified policy from the policy store.
|
default DeletePolicyResponse |
deletePolicy(DeletePolicyRequest deletePolicyRequest)
Deletes the specified policy from the policy store.
|
default DeletePolicyStoreResponse |
deletePolicyStore(Consumer<DeletePolicyStoreRequest.Builder> deletePolicyStoreRequest)
Deletes the specified policy store.
|
default DeletePolicyStoreResponse |
deletePolicyStore(DeletePolicyStoreRequest deletePolicyStoreRequest)
Deletes the specified policy store.
|
default DeletePolicyTemplateResponse |
deletePolicyTemplate(Consumer<DeletePolicyTemplateRequest.Builder> deletePolicyTemplateRequest)
Deletes the specified policy template from the policy store.
|
default DeletePolicyTemplateResponse |
deletePolicyTemplate(DeletePolicyTemplateRequest deletePolicyTemplateRequest)
Deletes the specified policy template from the policy store.
|
default GetIdentitySourceResponse |
getIdentitySource(Consumer<GetIdentitySourceRequest.Builder> getIdentitySourceRequest)
Retrieves the details about the specified identity source.
|
default GetIdentitySourceResponse |
getIdentitySource(GetIdentitySourceRequest getIdentitySourceRequest)
Retrieves the details about the specified identity source.
|
default GetPolicyResponse |
getPolicy(Consumer<GetPolicyRequest.Builder> getPolicyRequest)
Retrieves information about the specified policy.
|
default GetPolicyResponse |
getPolicy(GetPolicyRequest getPolicyRequest)
Retrieves information about the specified policy.
|
default GetPolicyStoreResponse |
getPolicyStore(Consumer<GetPolicyStoreRequest.Builder> getPolicyStoreRequest)
Retrieves details about a policy store.
|
default GetPolicyStoreResponse |
getPolicyStore(GetPolicyStoreRequest getPolicyStoreRequest)
Retrieves details about a policy store.
|
default GetPolicyTemplateResponse |
getPolicyTemplate(Consumer<GetPolicyTemplateRequest.Builder> getPolicyTemplateRequest)
Retrieve the details for the specified policy template in the specified policy store.
|
default GetPolicyTemplateResponse |
getPolicyTemplate(GetPolicyTemplateRequest getPolicyTemplateRequest)
Retrieve the details for the specified policy template in the specified policy store.
|
default GetSchemaResponse |
getSchema(Consumer<GetSchemaRequest.Builder> getSchemaRequest)
Retrieve the details for the specified schema in the specified policy store.
|
default GetSchemaResponse |
getSchema(GetSchemaRequest getSchemaRequest)
Retrieve the details for the specified schema in the specified policy store.
|
default IsAuthorizedResponse |
isAuthorized(Consumer<IsAuthorizedRequest.Builder> isAuthorizedRequest)
Makes an authorization decision about a service request described in the parameters.
|
default IsAuthorizedResponse |
isAuthorized(IsAuthorizedRequest isAuthorizedRequest)
Makes an authorization decision about a service request described in the parameters.
|
default IsAuthorizedWithTokenResponse |
isAuthorizedWithToken(Consumer<IsAuthorizedWithTokenRequest.Builder> isAuthorizedWithTokenRequest)
Makes an authorization decision about a service request described in the parameters.
|
default IsAuthorizedWithTokenResponse |
isAuthorizedWithToken(IsAuthorizedWithTokenRequest isAuthorizedWithTokenRequest)
Makes an authorization decision about a service request described in the parameters.
|
default ListIdentitySourcesResponse |
listIdentitySources(Consumer<ListIdentitySourcesRequest.Builder> listIdentitySourcesRequest)
Returns a paginated list of all of the identity sources defined in the specified policy store.
|
default ListIdentitySourcesResponse |
listIdentitySources(ListIdentitySourcesRequest listIdentitySourcesRequest)
Returns a paginated list of all of the identity sources defined in the specified policy store.
|
default ListIdentitySourcesIterable |
listIdentitySourcesPaginator(Consumer<ListIdentitySourcesRequest.Builder> listIdentitySourcesRequest)
Returns a paginated list of all of the identity sources defined in the specified policy store.
|
default ListIdentitySourcesIterable |
listIdentitySourcesPaginator(ListIdentitySourcesRequest listIdentitySourcesRequest)
Returns a paginated list of all of the identity sources defined in the specified policy store.
|
default ListPoliciesResponse |
listPolicies(Consumer<ListPoliciesRequest.Builder> listPoliciesRequest)
Returns a paginated list of all policies stored in the specified policy store.
|
default ListPoliciesResponse |
listPolicies(ListPoliciesRequest listPoliciesRequest)
Returns a paginated list of all policies stored in the specified policy store.
|
default ListPoliciesIterable |
listPoliciesPaginator(Consumer<ListPoliciesRequest.Builder> listPoliciesRequest)
Returns a paginated list of all policies stored in the specified policy store.
|
default ListPoliciesIterable |
listPoliciesPaginator(ListPoliciesRequest listPoliciesRequest)
Returns a paginated list of all policies stored in the specified policy store.
|
default ListPolicyStoresResponse |
listPolicyStores(Consumer<ListPolicyStoresRequest.Builder> listPolicyStoresRequest)
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
|
default ListPolicyStoresResponse |
listPolicyStores(ListPolicyStoresRequest listPolicyStoresRequest)
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
|
default ListPolicyStoresIterable |
listPolicyStoresPaginator(Consumer<ListPolicyStoresRequest.Builder> listPolicyStoresRequest)
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
|
default ListPolicyStoresIterable |
listPolicyStoresPaginator(ListPolicyStoresRequest listPolicyStoresRequest)
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
|
default ListPolicyTemplatesResponse |
listPolicyTemplates(Consumer<ListPolicyTemplatesRequest.Builder> listPolicyTemplatesRequest)
Returns a paginated list of all policy templates in the specified policy store.
|
default ListPolicyTemplatesResponse |
listPolicyTemplates(ListPolicyTemplatesRequest listPolicyTemplatesRequest)
Returns a paginated list of all policy templates in the specified policy store.
|
default ListPolicyTemplatesIterable |
listPolicyTemplatesPaginator(Consumer<ListPolicyTemplatesRequest.Builder> listPolicyTemplatesRequest)
Returns a paginated list of all policy templates in the specified policy store.
|
default ListPolicyTemplatesIterable |
listPolicyTemplatesPaginator(ListPolicyTemplatesRequest listPolicyTemplatesRequest)
Returns a paginated list of all policy templates in the specified policy store.
|
default PutSchemaResponse |
putSchema(Consumer<PutSchemaRequest.Builder> putSchemaRequest)
Creates or updates the policy schema in the specified policy store.
|
default PutSchemaResponse |
putSchema(PutSchemaRequest putSchemaRequest)
Creates or updates the policy schema in the specified policy store.
|
default VerifiedPermissionsServiceClientConfiguration |
serviceClientConfiguration() |
static ServiceMetadata |
serviceMetadata() |
default UpdateIdentitySourceResponse |
updateIdentitySource(Consumer<UpdateIdentitySourceRequest.Builder> updateIdentitySourceRequest)
Updates the specified identity source to use a new identity provider (IdP) source, or to change the mapping of
identities from the IdP to a different principal entity type.
|
default UpdateIdentitySourceResponse |
updateIdentitySource(UpdateIdentitySourceRequest updateIdentitySourceRequest)
Updates the specified identity source to use a new identity provider (IdP) source, or to change the mapping of
identities from the IdP to a different principal entity type.
|
default UpdatePolicyResponse |
updatePolicy(Consumer<UpdatePolicyRequest.Builder> updatePolicyRequest)
Modifies a Cedar static policy in the specified policy store.
|
default UpdatePolicyResponse |
updatePolicy(UpdatePolicyRequest updatePolicyRequest)
Modifies a Cedar static policy in the specified policy store.
|
default UpdatePolicyStoreResponse |
updatePolicyStore(Consumer<UpdatePolicyStoreRequest.Builder> updatePolicyStoreRequest)
Modifies the validation setting for a policy store.
|
default UpdatePolicyStoreResponse |
updatePolicyStore(UpdatePolicyStoreRequest updatePolicyStoreRequest)
Modifies the validation setting for a policy store.
|
default UpdatePolicyTemplateResponse |
updatePolicyTemplate(Consumer<UpdatePolicyTemplateRequest.Builder> updatePolicyTemplateRequest)
Updates the specified policy template.
|
default UpdatePolicyTemplateResponse |
updatePolicyTemplate(UpdatePolicyTemplateRequest updatePolicyTemplateRequest)
Updates the specified policy template.
|
serviceNameclosestatic final String SERVICE_NAME
static final String SERVICE_METADATA_ID
ServiceMetadataProvider.default CreateIdentitySourceResponse createIdentitySource(CreateIdentitySourceRequest createIdentitySourceRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Creates a reference to an Amazon Cognito user pool as an external 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 operation. These identities take the form of tokens that contain claims about the user, such as IDs, attributes and group memberships. Amazon Cognito provides both identity tokens and access tokens, and Verified Permissions can use either or both. Any combination of identity and access tokens results in the same Cedar principal. Verified Permissions automatically translates the information about the identities into the standard Cedar attributes that can be evaluated by your policies. Because the Amazon Cognito identity and access tokens can contain different information, the tokens you choose to use determine which principal attributes are available to access when evaluating Cedar policies.
If you delete a Amazon Cognito user pool or user, tokens from that deleted pool or that deleted user continue to be usable until they expire.
To reference a user from this identity source in your Cedar policies, use the following syntax.
IdentityType::"<CognitoUserPoolIdentifier>|<CognitoClientId>
Where IdentityType is the string that you provide to the PrincipalEntityType parameter
for this operation. The CognitoUserPoolId and CognitoClientId are defined by the Amazon
Cognito user pool.
createIdentitySourceRequest - 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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreateIdentitySourceResponse createIdentitySource(Consumer<CreateIdentitySourceRequest.Builder> createIdentitySourceRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Creates a reference to an Amazon Cognito user pool as an external 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 operation. These identities take the form of tokens that contain claims about the user, such as IDs, attributes and group memberships. Amazon Cognito provides both identity tokens and access tokens, and Verified Permissions can use either or both. Any combination of identity and access tokens results in the same Cedar principal. Verified Permissions automatically translates the information about the identities into the standard Cedar attributes that can be evaluated by your policies. Because the Amazon Cognito identity and access tokens can contain different information, the tokens you choose to use determine which principal attributes are available to access when evaluating Cedar policies.
If you delete a Amazon Cognito user pool or user, tokens from that deleted pool or that deleted user continue to be usable until they expire.
To reference a user from this identity source in your Cedar policies, use the following syntax.
IdentityType::"<CognitoUserPoolIdentifier>|<CognitoClientId>
Where IdentityType is the string that you provide to the PrincipalEntityType parameter
for this operation. The CognitoUserPoolId and CognitoClientId are defined by the Amazon
Cognito user pool.
This is a convenience which creates an instance of the CreateIdentitySourceRequest.Builder avoiding the
need to create one manually via CreateIdentitySourceRequest.builder()
createIdentitySourceRequest - A Consumer that will call methods on CreateIdentitySourceInput.Builder to create a
request.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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreatePolicyResponse createPolicy(CreatePolicyRequest createPolicyRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
Creating a policy causes it to be validated against the schema in the policy store. If the policy doesn't pass validation, the operation fails and the policy isn't stored.
createPolicyRequest - 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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreatePolicyResponse createPolicy(Consumer<CreatePolicyRequest.Builder> createPolicyRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
Creating a policy causes it to be validated against the schema in the policy store. If the policy doesn't pass validation, the operation fails and the policy isn't stored.
This is a convenience which creates an instance of the CreatePolicyRequest.Builder avoiding the need to
create one manually via CreatePolicyRequest.builder()
createPolicyRequest - A Consumer that will call methods on CreatePolicyInput.Builder to create a request.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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreatePolicyStoreResponse createPolicyStore(CreatePolicyStoreRequest createPolicyStoreRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Creates a policy store. A policy store is a container for policy resources.
createPolicyStoreRequest - 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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreatePolicyStoreResponse createPolicyStore(Consumer<CreatePolicyStoreRequest.Builder> createPolicyStoreRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Creates a policy store. A policy store is a container for policy resources.
This is a convenience which creates an instance of the CreatePolicyStoreRequest.Builder avoiding the need
to create one manually via CreatePolicyStoreRequest.builder()
createPolicyStoreRequest - A Consumer that will call methods on CreatePolicyStoreInput.Builder to create a request.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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreatePolicyTemplateResponse createPolicyTemplate(CreatePolicyTemplateRequest createPolicyTemplateRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
createPolicyTemplateRequest - 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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault CreatePolicyTemplateResponse createPolicyTemplate(Consumer<CreatePolicyTemplateRequest.Builder> createPolicyTemplateRequest) throws ValidationException, ServiceQuotaExceededException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
This is a convenience which creates an instance of the CreatePolicyTemplateRequest.Builder avoiding the
need to create one manually via CreatePolicyTemplateRequest.builder()
createPolicyTemplateRequest - A Consumer that will call methods on CreatePolicyTemplateInput.Builder to create a
request.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.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeleteIdentitySourceResponse deleteIdentitySource(DeleteIdentitySourceRequest deleteIdentitySourceRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
deleteIdentitySourceRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeleteIdentitySourceResponse deleteIdentitySource(Consumer<DeleteIdentitySourceRequest.Builder> deleteIdentitySourceRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
This is a convenience which creates an instance of the DeleteIdentitySourceRequest.Builder avoiding the
need to create one manually via DeleteIdentitySourceRequest.builder()
deleteIdentitySourceRequest - A Consumer that will call methods on DeleteIdentitySourceInput.Builder to create a
request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeletePolicyResponse deletePolicy(DeletePolicyRequest deletePolicyRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
deletePolicyRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeletePolicyResponse deletePolicy(Consumer<DeletePolicyRequest.Builder> deletePolicyRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
This is a convenience which creates an instance of the DeletePolicyRequest.Builder avoiding the need to
create one manually via DeletePolicyRequest.builder()
deletePolicyRequest - A Consumer that will call methods on DeletePolicyInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeletePolicyStoreResponse deletePolicyStore(DeletePolicyStoreRequest deletePolicyStoreRequest) throws ValidationException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
deletePolicyStoreRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeletePolicyStoreResponse deletePolicyStore(Consumer<DeletePolicyStoreRequest.Builder> deletePolicyStoreRequest) throws ValidationException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
This is a convenience which creates an instance of the DeletePolicyStoreRequest.Builder avoiding the need
to create one manually via DeletePolicyStoreRequest.builder()
deletePolicyStoreRequest - A Consumer that will call methods on DeletePolicyStoreInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeletePolicyTemplateResponse deletePolicyTemplate(DeletePolicyTemplateRequest deletePolicyTemplateRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Deletes the specified policy template from the policy store.
This operation also deletes any policies that were created from the specified policy template. Those policies are immediately removed from all future API responses, and are asynchronously deleted from the policy store.
deletePolicyTemplateRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault DeletePolicyTemplateResponse deletePolicyTemplate(Consumer<DeletePolicyTemplateRequest.Builder> deletePolicyTemplateRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Deletes the specified policy template from the policy store.
This operation also deletes any policies that were created from the specified policy template. Those policies are immediately removed from all future API responses, and are asynchronously deleted from the policy store.
This is a convenience which creates an instance of the DeletePolicyTemplateRequest.Builder avoiding the
need to create one manually via DeletePolicyTemplateRequest.builder()
deletePolicyTemplateRequest - A Consumer that will call methods on DeletePolicyTemplateInput.Builder to create a
request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetIdentitySourceResponse getIdentitySource(GetIdentitySourceRequest getIdentitySourceRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieves the details about the specified identity source.
getIdentitySourceRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetIdentitySourceResponse getIdentitySource(Consumer<GetIdentitySourceRequest.Builder> getIdentitySourceRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieves the details about the specified identity source.
This is a convenience which creates an instance of the GetIdentitySourceRequest.Builder avoiding the need
to create one manually via GetIdentitySourceRequest.builder()
getIdentitySourceRequest - A Consumer that will call methods on GetIdentitySourceInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetPolicyResponse getPolicy(GetPolicyRequest getPolicyRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieves information about the specified policy.
getPolicyRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetPolicyResponse getPolicy(Consumer<GetPolicyRequest.Builder> getPolicyRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieves information about the specified policy.
This is a convenience which creates an instance of the GetPolicyRequest.Builder avoiding the need to
create one manually via GetPolicyRequest.builder()
getPolicyRequest - A Consumer that will call methods on GetPolicyInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetPolicyStoreResponse getPolicyStore(GetPolicyStoreRequest getPolicyStoreRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieves details about a policy store.
getPolicyStoreRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetPolicyStoreResponse getPolicyStore(Consumer<GetPolicyStoreRequest.Builder> getPolicyStoreRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieves details about a policy store.
This is a convenience which creates an instance of the GetPolicyStoreRequest.Builder avoiding the need to
create one manually via GetPolicyStoreRequest.builder()
getPolicyStoreRequest - A Consumer that will call methods on GetPolicyStoreInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetPolicyTemplateResponse getPolicyTemplate(GetPolicyTemplateRequest getPolicyTemplateRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieve the details for the specified policy template in the specified policy store.
getPolicyTemplateRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetPolicyTemplateResponse getPolicyTemplate(Consumer<GetPolicyTemplateRequest.Builder> getPolicyTemplateRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieve the details for the specified policy template in the specified policy store.
This is a convenience which creates an instance of the GetPolicyTemplateRequest.Builder avoiding the need
to create one manually via GetPolicyTemplateRequest.builder()
getPolicyTemplateRequest - A Consumer that will call methods on GetPolicyTemplateInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetSchemaResponse getSchema(GetSchemaRequest getSchemaRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieve the details for the specified schema in the specified policy store.
getSchemaRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault GetSchemaResponse getSchema(Consumer<GetSchemaRequest.Builder> getSchemaRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Retrieve the details for the specified schema in the specified policy store.
This is a convenience which creates an instance of the GetSchemaRequest.Builder avoiding the need to
create one manually via GetSchemaRequest.builder()
getSchemaRequest - A Consumer that will call methods on GetSchemaInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault IsAuthorizedResponse isAuthorized(IsAuthorizedRequest isAuthorizedRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
isAuthorizedRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault IsAuthorizedResponse isAuthorized(Consumer<IsAuthorizedRequest.Builder> isAuthorizedRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
This is a convenience which creates an instance of the IsAuthorizedRequest.Builder avoiding the need to
create one manually via IsAuthorizedRequest.builder()
isAuthorizedRequest - A Consumer that will call methods on IsAuthorizedInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault IsAuthorizedWithTokenResponse isAuthorizedWithToken(IsAuthorizedWithTokenRequest isAuthorizedWithTokenRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Makes an authorization decision about a service request described in the parameters. The principal in this
request comes from an external identity source. 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.
If you delete a Amazon Cognito user pool or user, tokens from that deleted pool or that deleted user continue to be usable until they expire.
isAuthorizedWithTokenRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault IsAuthorizedWithTokenResponse isAuthorizedWithToken(Consumer<IsAuthorizedWithTokenRequest.Builder> isAuthorizedWithTokenRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Makes an authorization decision about a service request described in the parameters. The principal in this
request comes from an external identity source. 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.
If you delete a Amazon Cognito user pool or user, tokens from that deleted pool or that deleted user continue to be usable until they expire.
This is a convenience which creates an instance of the IsAuthorizedWithTokenRequest.Builder avoiding the
need to create one manually via IsAuthorizedWithTokenRequest.builder()
isAuthorizedWithTokenRequest - A Consumer that will call methods on IsAuthorizedWithTokenInput.Builder to create a
request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListIdentitySourcesResponse listIdentitySources(ListIdentitySourcesRequest listIdentitySourcesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all of the identity sources defined in the specified policy store.
listIdentitySourcesRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListIdentitySourcesResponse listIdentitySources(Consumer<ListIdentitySourcesRequest.Builder> listIdentitySourcesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all of the identity sources defined in the specified policy store.
This is a convenience which creates an instance of the ListIdentitySourcesRequest.Builder avoiding the
need to create one manually via ListIdentitySourcesRequest.builder()
listIdentitySourcesRequest - A Consumer that will call methods on ListIdentitySourcesInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListIdentitySourcesIterable listIdentitySourcesPaginator(ListIdentitySourcesRequest listIdentitySourcesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all of the identity sources defined in the specified policy store.
This is a variant of
listIdentitySources(software.amazon.awssdk.services.verifiedpermissions.model.ListIdentitySourcesRequest)
operation. The return type is a custom iterable that can be used to iterate through all the pages. SDK will
internally handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListIdentitySourcesIterable responses = client.listIdentitySourcesPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListIdentitySourcesIterable responses = client
.listIdentitySourcesPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListIdentitySourcesResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListIdentitySourcesIterable responses = client.listIdentitySourcesPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listIdentitySources(software.amazon.awssdk.services.verifiedpermissions.model.ListIdentitySourcesRequest)
operation.
listIdentitySourcesRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListIdentitySourcesIterable listIdentitySourcesPaginator(Consumer<ListIdentitySourcesRequest.Builder> listIdentitySourcesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all of the identity sources defined in the specified policy store.
This is a variant of
listIdentitySources(software.amazon.awssdk.services.verifiedpermissions.model.ListIdentitySourcesRequest)
operation. The return type is a custom iterable that can be used to iterate through all the pages. SDK will
internally handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListIdentitySourcesIterable responses = client.listIdentitySourcesPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListIdentitySourcesIterable responses = client
.listIdentitySourcesPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListIdentitySourcesResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListIdentitySourcesIterable responses = client.listIdentitySourcesPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listIdentitySources(software.amazon.awssdk.services.verifiedpermissions.model.ListIdentitySourcesRequest)
operation.
This is a convenience which creates an instance of the ListIdentitySourcesRequest.Builder avoiding the
need to create one manually via ListIdentitySourcesRequest.builder()
listIdentitySourcesRequest - A Consumer that will call methods on ListIdentitySourcesInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPoliciesResponse listPolicies(ListPoliciesRequest listPoliciesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policies stored in the specified policy store.
listPoliciesRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPoliciesResponse listPolicies(Consumer<ListPoliciesRequest.Builder> listPoliciesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policies stored in the specified policy store.
This is a convenience which creates an instance of the ListPoliciesRequest.Builder avoiding the need to
create one manually via ListPoliciesRequest.builder()
listPoliciesRequest - A Consumer that will call methods on ListPoliciesInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPoliciesIterable listPoliciesPaginator(ListPoliciesRequest listPoliciesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policies stored in the specified policy store.
This is a variant of
listPolicies(software.amazon.awssdk.services.verifiedpermissions.model.ListPoliciesRequest) operation.
The return type is a custom iterable that can be used to iterate through all the pages. SDK will internally
handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPoliciesIterable responses = client.listPoliciesPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPoliciesIterable responses = client
.listPoliciesPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListPoliciesResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPoliciesIterable responses = client.listPoliciesPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listPolicies(software.amazon.awssdk.services.verifiedpermissions.model.ListPoliciesRequest)
operation.
listPoliciesRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPoliciesIterable listPoliciesPaginator(Consumer<ListPoliciesRequest.Builder> listPoliciesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policies stored in the specified policy store.
This is a variant of
listPolicies(software.amazon.awssdk.services.verifiedpermissions.model.ListPoliciesRequest) operation.
The return type is a custom iterable that can be used to iterate through all the pages. SDK will internally
handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPoliciesIterable responses = client.listPoliciesPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPoliciesIterable responses = client
.listPoliciesPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListPoliciesResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPoliciesIterable responses = client.listPoliciesPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listPolicies(software.amazon.awssdk.services.verifiedpermissions.model.ListPoliciesRequest)
operation.
This is a convenience which creates an instance of the ListPoliciesRequest.Builder avoiding the need to
create one manually via ListPoliciesRequest.builder()
listPoliciesRequest - A Consumer that will call methods on ListPoliciesInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyStoresResponse listPolicyStores(ListPolicyStoresRequest listPolicyStoresRequest) throws ValidationException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
listPolicyStoresRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyStoresResponse listPolicyStores(Consumer<ListPolicyStoresRequest.Builder> listPolicyStoresRequest) throws ValidationException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
This is a convenience which creates an instance of the ListPolicyStoresRequest.Builder avoiding the need
to create one manually via ListPolicyStoresRequest.builder()
listPolicyStoresRequest - A Consumer that will call methods on ListPolicyStoresInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyStoresIterable listPolicyStoresPaginator(ListPolicyStoresRequest listPolicyStoresRequest) throws ValidationException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
This is a variant of
listPolicyStores(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyStoresRequest)
operation. The return type is a custom iterable that can be used to iterate through all the pages. SDK will
internally handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyStoresIterable responses = client.listPolicyStoresPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyStoresIterable responses = client
.listPolicyStoresPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyStoresResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyStoresIterable responses = client.listPolicyStoresPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listPolicyStores(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyStoresRequest)
operation.
listPolicyStoresRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyStoresIterable listPolicyStoresPaginator(Consumer<ListPolicyStoresRequest.Builder> listPolicyStoresRequest) throws ValidationException, AccessDeniedException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy stores in the calling Amazon Web Services account.
This is a variant of
listPolicyStores(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyStoresRequest)
operation. The return type is a custom iterable that can be used to iterate through all the pages. SDK will
internally handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyStoresIterable responses = client.listPolicyStoresPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyStoresIterable responses = client
.listPolicyStoresPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyStoresResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyStoresIterable responses = client.listPolicyStoresPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listPolicyStores(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyStoresRequest)
operation.
This is a convenience which creates an instance of the ListPolicyStoresRequest.Builder avoiding the need
to create one manually via ListPolicyStoresRequest.builder()
listPolicyStoresRequest - A Consumer that will call methods on ListPolicyStoresInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyTemplatesResponse listPolicyTemplates(ListPolicyTemplatesRequest listPolicyTemplatesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy templates in the specified policy store.
listPolicyTemplatesRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyTemplatesResponse listPolicyTemplates(Consumer<ListPolicyTemplatesRequest.Builder> listPolicyTemplatesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy templates in the specified policy store.
This is a convenience which creates an instance of the ListPolicyTemplatesRequest.Builder avoiding the
need to create one manually via ListPolicyTemplatesRequest.builder()
listPolicyTemplatesRequest - A Consumer that will call methods on ListPolicyTemplatesInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyTemplatesIterable listPolicyTemplatesPaginator(ListPolicyTemplatesRequest listPolicyTemplatesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy templates in the specified policy store.
This is a variant of
listPolicyTemplates(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyTemplatesRequest)
operation. The return type is a custom iterable that can be used to iterate through all the pages. SDK will
internally handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyTemplatesIterable responses = client.listPolicyTemplatesPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyTemplatesIterable responses = client
.listPolicyTemplatesPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyTemplatesResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyTemplatesIterable responses = client.listPolicyTemplatesPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listPolicyTemplates(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyTemplatesRequest)
operation.
listPolicyTemplatesRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault ListPolicyTemplatesIterable listPolicyTemplatesPaginator(Consumer<ListPolicyTemplatesRequest.Builder> listPolicyTemplatesRequest) throws ValidationException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Returns a paginated list of all policy templates in the specified policy store.
This is a variant of
listPolicyTemplates(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyTemplatesRequest)
operation. The return type is a custom iterable that can be used to iterate through all the pages. SDK will
internally handle making service calls for you.
When this operation is called, a custom iterable is returned but no service calls are made yet. So there is no guarantee that the request is valid. As you iterate through the iterable, SDK will start lazily loading response pages by making service calls until there are no pages left or your iteration stops. If there are errors in your request, you will see the failures only after you start iterating through the iterable.
The following are few ways to iterate through the response pages:
1) Using a Stream
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyTemplatesIterable responses = client.listPolicyTemplatesPaginator(request);
responses.stream().forEach(....);
2) Using For loop
{
@code
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyTemplatesIterable responses = client
.listPolicyTemplatesPaginator(request);
for (software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyTemplatesResponse response : responses) {
// do something;
}
}
3) Use iterator directly
software.amazon.awssdk.services.verifiedpermissions.paginators.ListPolicyTemplatesIterable responses = client.listPolicyTemplatesPaginator(request);
responses.iterator().forEachRemaining(....);
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listPolicyTemplates(software.amazon.awssdk.services.verifiedpermissions.model.ListPolicyTemplatesRequest)
operation.
This is a convenience which creates an instance of the ListPolicyTemplatesRequest.Builder avoiding the
need to create one manually via ListPolicyTemplatesRequest.builder()
listPolicyTemplatesRequest - A Consumer that will call methods on ListPolicyTemplatesInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault PutSchemaResponse putSchema(PutSchemaRequest putSchemaRequest) throws ValidationException, ServiceQuotaExceededException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
putSchemaRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault PutSchemaResponse putSchema(Consumer<PutSchemaRequest.Builder> putSchemaRequest) throws ValidationException, ServiceQuotaExceededException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
This is a convenience which creates an instance of the PutSchemaRequest.Builder avoiding the need to
create one manually via PutSchemaRequest.builder()
putSchemaRequest - A Consumer that will call methods on PutSchemaInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdateIdentitySourceResponse updateIdentitySource(UpdateIdentitySourceRequest updateIdentitySourceRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Updates the specified identity source to use a new identity provider (IdP) source, or to change the mapping of identities from the IdP to a different principal entity type.
updateIdentitySourceRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdateIdentitySourceResponse updateIdentitySource(Consumer<UpdateIdentitySourceRequest.Builder> updateIdentitySourceRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Updates the specified identity source to use a new identity provider (IdP) source, or to change the mapping of identities from the IdP to a different principal entity type.
This is a convenience which creates an instance of the UpdateIdentitySourceRequest.Builder avoiding the
need to create one manually via UpdateIdentitySourceRequest.builder()
updateIdentitySourceRequest - A Consumer that will call methods on UpdateIdentitySourceInput.Builder to create a
request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdatePolicyResponse updatePolicy(UpdatePolicyRequest updatePolicyRequest) throws ValidationException, ServiceQuotaExceededException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
If policy validation is enabled in the policy store, then updating a static policy causes Verified Permissions to validate the policy against the schema in the policy store. If the updated static policy doesn't pass validation, the operation fails and the update isn't stored.
updatePolicyRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdatePolicyResponse updatePolicy(Consumer<UpdatePolicyRequest.Builder> updatePolicyRequest) throws ValidationException, ServiceQuotaExceededException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
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.
If policy validation is enabled in the policy store, then updating a static policy causes Verified Permissions to validate the policy against the schema in the policy store. If the updated static policy doesn't pass validation, the operation fails and the update isn't stored.
This is a convenience which creates an instance of the UpdatePolicyRequest.Builder avoiding the need to
create one manually via UpdatePolicyRequest.builder()
updatePolicyRequest - A Consumer that will call methods on UpdatePolicyInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdatePolicyStoreResponse updatePolicyStore(UpdatePolicyStoreRequest updatePolicyStoreRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Modifies the validation setting for a policy store.
updatePolicyStoreRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdatePolicyStoreResponse updatePolicyStore(Consumer<UpdatePolicyStoreRequest.Builder> updatePolicyStoreRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Modifies the validation setting for a policy store.
This is a convenience which creates an instance of the UpdatePolicyStoreRequest.Builder avoiding the need
to create one manually via UpdatePolicyStoreRequest.builder()
updatePolicyStoreRequest - A Consumer that will call methods on UpdatePolicyStoreInput.Builder to create a request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdatePolicyTemplateResponse updatePolicyTemplate(UpdatePolicyTemplateRequest updatePolicyTemplateRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Updates the specified policy template. You can update only the description and the some elements of the policyBody.
Changes you make to the policy template content are immediately reflected in authorization decisions that involve all template-linked policies instantiated from this template.
updatePolicyTemplateRequest - 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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptiondefault UpdatePolicyTemplateResponse updatePolicyTemplate(Consumer<UpdatePolicyTemplateRequest.Builder> updatePolicyTemplateRequest) throws ValidationException, ConflictException, AccessDeniedException, ResourceNotFoundException, ThrottlingException, InternalServerException, AwsServiceException, SdkClientException, VerifiedPermissionsException
Updates the specified policy template. You can update only the description and the some elements of the policyBody.
Changes you make to the policy template content are immediately reflected in authorization decisions that involve all template-linked policies instantiated from this template.
This is a convenience which creates an instance of the UpdatePolicyTemplateRequest.Builder avoiding the
need to create one manually via UpdatePolicyTemplateRequest.builder()
updatePolicyTemplateRequest - A Consumer that will call methods on UpdatePolicyTemplateInput.Builder to create a
request.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 laterSdkException - Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for
catch all scenarios.SdkClientException - If any client side error occurs such as an IO related failure, failure to get credentials, etc.VerifiedPermissionsException - Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.AwsServiceExceptionstatic VerifiedPermissionsClient create()
VerifiedPermissionsClient with the region loaded from the
DefaultAwsRegionProviderChain and credentials loaded from the
DefaultCredentialsProvider.static VerifiedPermissionsClientBuilder builder()
VerifiedPermissionsClient.static ServiceMetadata serviceMetadata()
default VerifiedPermissionsServiceClientConfiguration serviceClientConfiguration()
serviceClientConfiguration in interface AwsClientserviceClientConfiguration in interface SdkClientCopyright © 2023. All rights reserved.