Skip to content

Commit 19654de

Browse files
authored
Amazon S3 Vectors and Unstructured: added missing step for non-filterable metadata (#693)
1 parent c10a317 commit 19654de

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

examplecode/tools/s3-vectors.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -69,9 +69,12 @@ To use this example, you will need:
6969
5. Select the appropriate **Distance metric** for your embedding model. For example, for the
7070
**Titan Text Embeddings V2** (`amazon.titan-embed-text-v2:0`) embedding model, select **Cosine**. If you are not sure which distance metric to use,
7171
see your embedding model's documentation.
72-
8. Click **Create vector index**.
73-
9. After the vector index is created, copy the value of the index's **Amazon Resource Name (ARN)**, as you will need it in
74-
later steps. This ARN takes the format `arn:aws:s3vectors:<region-id>:<account>:bucket/<bucket-name>/index/<index-name>`.
72+
6. Expand **Additional settings**.
73+
7. Within **Metadata configuration**, under **Non-filterable metadata**, click **Add key**.
74+
8. For **Key**, enter `text`. This allows you to query the vector index by the `text` field within each object that will be coming over into the index from the JSON output files.
75+
9. Click **Create vector index**.
76+
10. After the vector index is created, copy the value of the index's **Amazon Resource Name (ARN)**, as you will need it in
77+
later steps. This ARN takes the format `arn:aws:s3vectors:<region-id>:<account>:bucket/<bucket-name>/index/<index-name>`.
7578

7679
## Step 3: Add the source JSON output files' contents to the vector index
7780

0 commit comments

Comments
 (0)