CreateAccessControlConfiguration
Creates an access configuration for your documents. This includes user and group access information for your documents. This is useful for user context filtering, where search results are filtered based on the user or their group access to documents.
You can use this to re-configure your existing document level access control without indexing all of your documents again. For example, your index contains top-secret company documents that only certain employees or users should access. One of these users leaves the company or switches to a team that should be blocked from accessing top-secret documents. The user still has access to top-secret documents because the user had access when your documents were previously indexed. You can create a specific access control configuration for the user with deny access. You can later update the access control configuration to allow access if the user returns to the company and re-joins the 'top-secret' team. You can re-configure access control for your documents as circumstances change.
To apply your access control configuration to certain documents, you call the BatchPutDocument API with the AccessControlConfigurationId
included in the Document object. If you use an S3 bucket as a data source, you update the
.metadata.json
with the AccessControlConfigurationId
and
synchronize your data source. Amazon Kendra currently only supports access control
configuration for S3 data sources and documents indexed using the
BatchPutDocument
API.
Request Syntax
{
"AccessControlList": [
{
"Access": "string
",
"DataSourceId": "string
",
"Name": "string
",
"Type": "string
"
}
],
"ClientToken": "string
",
"Description": "string
",
"HierarchicalAccessControlList": [
{
"PrincipalList": [
{
"Access": "string
",
"DataSourceId": "string
",
"Name": "string
",
"Type": "string
"
}
]
}
],
"IndexId": "string
",
"Name": "string
"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- AccessControlList
-
Information on principals (users and/or groups) and which documents they should have access to. This is useful for user context filtering, where search results are filtered based on the user or their group access to documents.
Type: Array of Principal objects
Required: No
- ClientToken
-
A token that you provide to identify the request to create an access control configuration. Multiple calls to the
CreateAccessControlConfiguration
API with the same client token will create only one access control configuration.Type: String
Length Constraints: Minimum length of 1. Maximum length of 100.
Required: No
- Description
-
A description for the access control configuration.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 1000.
Pattern:
^\P{C}*$
Required: No
- HierarchicalAccessControlList
-
The list of principal lists that define the hierarchy for which documents users should have access to.
Type: Array of HierarchicalPrincipal objects
Array Members: Minimum number of 1 item. Maximum number of 30 items.
Required: No
- IndexId
-
The identifier of the index to create an access control configuration for your documents.
Type: String
Length Constraints: Fixed length of 36.
Pattern:
[a-zA-Z0-9][a-zA-Z0-9-]*
Required: Yes
- Name
-
A name for the access control configuration.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 200.
Pattern:
[\S\s]*
Required: Yes
Response Syntax
{
"Id": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- Id
-
The identifier of the access control configuration for your documents in an index.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 36.
Pattern:
[a-zA-Z0-9-]+
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
You don't have sufficient access to perform this action. Please ensure you have the required permission policies and user accounts and try again.
HTTP Status Code: 400
- ConflictException
-
A conflict occurred with the request. Please fix any inconsistences with your resources and try again.
HTTP Status Code: 400
- InternalServerException
-
An issue occurred with the internal server used for your Amazon Kendra service. Please wait a few minutes and try again, or contact Support
for help. HTTP Status Code: 500
- ResourceNotFoundException
-
The resource you want to use doesn’t exist. Please check you have provided the correct resource and try again.
HTTP Status Code: 400
- ServiceQuotaExceededException
-
You have exceeded the set limits for your Amazon Kendra service. Please see Quotas for more information, or contact Support
to inquire about an increase of limits. HTTP Status Code: 400
- ThrottlingException
-
The request was denied due to request throttling. Please reduce the number of requests and try again.
HTTP Status Code: 400
- ValidationException
-
The input fails to satisfy the constraints set by the Amazon Kendra service. Please provide the correct input and try again.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: