Creates an Amazon Kendra index. Index creation is an asynchronous API. To determine if index creation has completed, check the Status
field returned from a call to describe_index
. The Status
field is set to ACTIVE
when the index is ready to use.
See https://www.paws-r-sdk.com/docs/kendra_create_index/ for full documentation.
kendra_create_index(
Name,
Edition = NULL,
RoleArn,
ServerSideEncryptionConfiguration = NULL,
Description = NULL,
ClientToken = NULL,
Tags = NULL,
UserTokenConfigurations = NULL,
UserContextPolicy = NULL,
UserGroupResolutionConfiguration = NULL
)
[required] A name for the index.
The Amazon Kendra edition to use for the index. Choose
DEVELOPER_EDITION
for indexes intended for development, testing, or
proof of concept. Use ENTERPRISE_EDITION
for production. Once you set
the edition for an index, it can't be changed.
The Edition
parameter is optional. If you don't supply a value, the
default is ENTERPRISE_EDITION
.
For more information on quota limits for Enterprise and Developer editions, see Quotas.
[required] The Amazon Resource Name (ARN) of an IAM role with permission to access your Amazon CloudWatch logs and metrics. For more information, see IAM access roles for Amazon Kendra.
The identifier of the KMS customer managed key (CMK) that's used to encrypt data indexed by Amazon Kendra. Amazon Kendra doesn't support asymmetric CMKs.
A description for the index.
A token that you provide to identify the request to create an index.
Multiple calls to the create_index
API with the
same client token will create only one index.
A list of key-value pairs that identify or categorize the index. You can also use tags to help control access to the index. Tag keys and values can consist of Unicode letters, digits, white space, and any of the following symbols: _ . : / = + - @.
The user token configuration.
The user context policy.
ATTRIBUTE_FILTER
All indexed content is searchable and displayable for all users. If you
want to filter search results on user context, you can use the attribute
filters of _user_id
and _group_ids
or you can provide user and group
information in UserContext
.
USER_TOKEN
Enables token-based user access control to filter search results on user context. All documents with no access control and all documents accessible to the user will be searchable and displayable.
Gets users and groups from IAM Identity Center (successor to Single Sign-On) identity source. To configure this, see UserGroupResolutionConfiguration.