Requirements and limitations
Keep the following requirements and limitations in mind when you work with vector indexes:
-
Vector indexes are supported only on tables that use on-demand capacity mode.
-
Vector embeddings are stored in the index at 32-bit floating point (f32) precision. Higher-precision values are accepted but lose precision when replicated to the index.
-
Fine-grained access control (FGAC) is not supported for the
SearchVectorsAPI. -
SearchVectorsresponses are limited to 16 MB. Pagination is not supported. Because each result includes the projected attributes, usingProjectionType: ALLwith large items and a highTopKvalue can approach this limit. If your items are large, use a narrower projection or reduceTopK. -
Vector indexes do not support
QueryorScanoperations. Use theSearchVectorsAPI to read from vector indexes. -
Vector indexes are not accessible through PartiQL. Use the
SearchVectorsAPI to run similarity searches.
For numeric limits including maximum dimensions, TopK range, inline filters per index, indexes per table, and base table size thresholds, see Vector indexes in Quotas in Amazon DynamoDB.