Querying an index
Note
Feature support varies by index type and search API being used. To see if this feature is supported for the index type and search API you’re using, see Index types.
When you search your index, Amazon Kendra uses all the information that you provided about your documents to determine the documents most relevant to the search terms entered. Some of the items that Amazon Kendra considers are:
-
The text or body of the document.
-
The title of the document.
-
Custom text fields that you have marked as searchable.
-
The date field that you have indicated should be used to determine the "freshness" of a document.
-
Any other field that could provide relevant information.
Amazon Kendra can also filter the response based on any field/attribute filters that you might have set for the search. For example, if you have a custom field called "department", you can filter the response to return only documents from a department called "legal". For more information, see Custom fields or attributes.
Returned search results are sorted by the relevance that Amazon Kendra determines for each document. The results are paginated so that you can show a page at a time to your user.
To search documents that you have indexed with Amazon Kendra for Amazon Lex, use AMAZON.KendraSearchIntent. For an example of configuring Amazon Kendra with Amazon Lex, see Creating a FAQ Bot for an Amazon Kendra Index.
The following example shows how to search an index. Amazon Kendra determines the type of the search result (answer, document, question-answer) that's best suited for the query. You can't configure Amazon Kendra to return a specific type of search response (answer, document, question-answer) to a query.
For information about the query responses, see Query responses and response types.
Topics
Prerequisites
Before using the Query API to query an index:
-
Set up the required permissions for an index and connect to your data source or batch upload your documents. For more information, see IAM roles. You use the Amazon Resource Name of the role when you call the API to create an index and data source connector or batch upload of documents.
-
Set up either the AWS Command Line Interface, an SDK, or go to the Amazon Kendra console. For more information, see Setting up Amazon Kendra.
-
Create an index and connect to a data source of documents or batch upload documents. For more information, see Creating an index and Creating a data source connector.
Searching an index (console)
You can use the Amazon Kendra console to search and test your index. You can make queries and see the results.
To search an index with the console
-
Sign in to the AWS Management Console and open the Amazon Kendra console at http://console.aws.amazon.com/kendra/
. -
On the navigation pane, choose Indexes.
-
Choose your index.
-
In the navigation menu, choose the option to search your index.
-
Enter a query in the text box and then press enter.
-
Amazon Kendra returns the results of the search.
You can also get the query ID for the search by selecting the lightbulb icon in the side panel.
Searching an index (SDK)
To search an index with Python or Java
-
The following example searches an index. Change the value of
query
to your search query andindex_id
orindexId
to the index identifier of the index that you want to search.You can also get the query ID for the search as part of the response elements when you call the Query API.
Searching an index (Postman)
You can use Postman
To search an index using Postman
-
Create a new collection in Postman and set the request type to POST.
-
Enter the endpoint URL. For example, https://kendra.<region>.amazonaws.com.
-
Select the Authorization tab and enter the following information.
-
Type—Select AWS signature.
-
AccessKey—Enter the access key generated when you create an IAM user.
-
SecretKey—Enter the secret key generated when you create an IAM user.
-
AWS Region—Enter the region of you index. For example, us-west-2.
-
Service Name—Enter kendra. This is case sensitive, so must be lower case.
Warning
If you enter the incorrect service name or don't use lowercase, an error is thrown once you select Send to send the request: "Credential should be scoped to the correct service 'kendra'."
You must also check that you entered the correct access key and secret key.
-
-
Select the Headers tab and enter the following key and value information.
-
Key: X-Amz-Target
Value: com.amazonaws.kendra.AWSKendraFrontendService.Query
-
Key: Content-Encoding
Value: amz-1.0
-
-
Select the Body tab and do the following.
-
Choose the raw JSON type for the body of the request.
-
Enter a JSON that includes your index ID and query text.
{ "IndexId": "
index-id
", "QueryText": "enter a query here" }Warning
If your JSON doesn't use the correct indendation, an error is thrown: "SerializationException". Check the indendation in your JSON.
-
-
Select Send (near the top right).
Searching with advanced query syntax
You can create queries that are more specific than simple keyword or natural language queries by using advanced query syntax or operators. This includes ranges, Booleans, wildcards, and more. By using operators, you can give your query more context and further refine the search results.
Amazon Kendra supports the following operators.
-
Boolean: Logic to limit or broaden the search. For example,
amazon AND sports
limits the search to only search for documents containing both terms. -
Parentheses: Reads nested query terms in order of precedence. For example,
(amazon AND sports) NOT rainforest
reads(amazon AND sports)
beforeNOT rainforest
. -
Ranges: Date or numeric range values. Ranges can be inclusive, exclusive, or unbounded. For example, you can search for documents that were last updated between January 1st 2020 and December 31st 2020, inclusive of these dates.
-
Fields: Uses a specific field to limit the search. For example, you can search for documents that have 'United States' in the field 'location'.
-
Wildcards: Partially match a string of text. For example,
Cloud*
could match CloudFormation. Amazon Kendra currently only supports trailing wildcards. -
Exact quotes: Exact match a string of text. For example, documents that contain
"Amazon Kendra" "pricing"
.
You can use a combination of any of the above operators.
Note that excessive use of operators or highly complex queries could impact query latency. Wildcards are some of the most expensive operators in terms of latency. A general rule is the more terms and operators that you use, the greater potential impact on latency. Other factors that affect latency include the average size of documents indexed, the size of your index, any filtering on search results, and the overall load on your Amazon Kendra index.
Boolean
You can combine or exclude words using the Boolean operators AND
,
OR
, NOT
.
The following are examples of using Boolean operators.
amazon AND sports
Returns search results that contain both the terms 'amazon' and 'sports' in the text, such as Amazon Prime video sports or other similar content.
sports OR recreation
Returns search results that contain the terms 'sports' or 'recreation', or both, in the text.
amazon NOT rainforest
Returns search results that contain the term 'amazon' but not the term 'rainforest' in the text. This is to search for documents about the company Amazon, not the Amazon Rainforest.
Parentheses
You can query nested words in order of precedence by using parentheses. The parentheses indicate to Amazon Kendra how a query should be read.
The following are examples of using parentheses operators.
(amazon AND sports) NOT rainforest
Returns documents that contain both the terms 'amazon' and 'sports' in the
text, but not the term 'rainforest'. This is to search Amazon Prime video sports
or other similar content, not adventure sports in the Amazon Rainforest. The
parentheses help indicate that amazon AND sports
should be read
before NOT rainforest
. The query should not be read as amazon
AND (sports NOT rainforest)
.
(amazon AND (sports OR recreation)) NOT
rainforest
Returns documents that contain the terms 'sports' or 'recreation', or both,
and the term 'amazon'. But it does not include the term 'rainforest'. This is to
search Amazon Prime video sports or recreation, not adventure sports in the
Amazon Rainforest. The parentheses help indicate that sports OR
recreation
should be read before combining with 'amazon', which is
read before NOT rainforest
. The query should not be read as
amazon AND (sports OR (recreation NOT rainforest))
.
Ranges
You can use a range of values to filter the search results. You specify an attribute and the range values. This can be date or numeric type.
Date ranges must be in the following formats:
-
Epoch
-
YYYY
-
YYYY-mm
-
YYYY-mm-dd
-
YYYY-mm-dd'T'HH
You can also specify whether to include or exclude the lower and higher values of the range.
The following are examples of using range operators.
_processed_date:>2019-12-31 AND
_processed_date:<2021-01-01
Returns documents that were processed in 2020—greater than December 31st 2019 and less than January 1st 2021.
_processed_date:>=2020-01-01 AND
_processed_date:<=2020-12-31
Returns documents that were processed in 2020—greater than or equal to January 1st 2020 and less than or equal to December 31st 2020.
_document_likes:<1
Returns documents with zero likes or no user feedback—less than 1 like.
You can specify whether a range should be treated as inclusive or exclusive of the given range values.
Inclusive
_last_updated_at:[2020-01-01 TO
2020-12-31]
Returns documents last updated in 2020—includes the days December 1st 2020 and December 31st 2020.
Exclusive
_last_updated_at:{2019-12-31 TO
2021-01-01}
Returns documents last updated in 2020—excludes the days December 31st 2019 and January 1st 2021.
For unbounded ranges that are neither inclusive or exclusive, simply use the
< and > operators. For example, _last_updated_at:>2019-12-31 AND
_last_updated_at:<2021-01-01
Fields
You can limit your search to only return documents that meet a value in a specific field. The field can be of any type.
The following are examples of using field-level context operators.
status:"Incomplete" AND
financial_year:2021
Returns documents for the 2021 financial year with their status as incomplete.
(sports OR recreation) AND country:"United
States" AND level:"professional"
Returns documents that discuss professional sports or recreation in the United States.
Wildcards
You can broaden your search to account for variants of words and phrases using the wildcard operator. This is useful when searching for name variants. Amazon Kendra currently only supports trailing wildcards. The number of prefix characters for a trailing wildcard must be greater than two.
The following are examples of using wildcard operators.
Cloud*
Returns documents that contain variants such as CloudFormation and CloudWatch.
kendra*aws
Returns documents that contain variants such as kendra.amazonaws.
kendra*aws*
Returns documents that contain variants such as kendra.amazonaws.com
Exact quotes
You can use quotation marks to search for an exact match of a piece of text.
The following are examples of using quotation marks.
"Amazon Kendra" "pricing"
Returns documents that contain both the phrase 'Amazon Kendra' and the term 'pricing'. Documents must contain both 'Amazon Kendra' and 'pricing' in order to return in the results.
"Amazon Kendra" "pricing"
cost
Returns documents that contain both the phrase 'Amazon Kendra' and the term 'pricing', and optionally the term 'cost'. Documents must contain both 'Amazon Kendra' and 'pricing' in order to return in the results, but might not necessarily include 'cost'.
Invalid query syntax
Amazon Kendra issues a warning if there are problems with your query syntax or your query is currently not supported by Amazon Kendra. For more information, see the API documentation for query warnings.
The following queries are examples of invalid query syntax.
_last_updated_at:<2021-12-32
Invalid date. Day 32 does not exist in the Gregorian calendar, which is used by Amazon Kendra.
_view_count:ten
Invalid numeric value. Digits must be used to represent numeric values.
nonExistentField:123
Invalid field search. The field must exist in order to use field search.
Product:[A TO D]
Invalid range. Numeric values or dates must be used for ranges.
OR Hello
Invalid Boolean. Operators must be used with terms and placed between terms.
Searching in languages
You can search for documents in a supported language. You pass the language code in the AttributeFilter to return filtered documents in your chosen language. You can type the query in a supported language.
If you do not specify a language, Amazon Kendra queries documents in English by default. For more information on supported languages, including their codes, see Adding documents in languages other than English.
To search for documents in a supported language in the console, select your index, then select the option to search your index from the navigation menu. Choose the language that you want to return documents by selecting the search settings and then selecting a language from the dropdown Language.
The following examples show how to search for documents in Spanish.
To search an index in Spanish in the console
-
Sign in to the AWS Management Console and open the Amazon Kendra console at http://console.aws.amazon.com/kendra/
. -
In the navigation menu, choose Indexes and choose your index.
-
In the navigation menu, choose the option to search your index.
-
In the search settings, select the Languages dropdown and choose Spanish.
-
Enter a query into the text box and then press enter.
-
Amazon Kendra returns the results of the search in Spanish.
To search an index in Spanish using the CLI, Python or Java
-
The following example searches an index in Spanish. Change the value
searchString
to your search query and the valueindexID
to the identifier of the index that you want to search. The language code for Spanish ises
. You can replace this with your own language code.