* s3vectors: enforce AWS metadata, key and filter limits
PutVectors accepted vector metadata of any size and key count, bounded
only by the request body limit, and keys of any length; QueryVectors
accepted filters of any size. Apply the AWS S3 Vectors limits
(https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors-limitations.html),
taking the ENHANCED index values where the modes differ, since this
implementation prefilters and takes no indexMode:
- 100 KB total metadata per vector, which also bounds a single
non-filterable field;
- 2 KB filterable metadata per vector;
- 50 metadata keys per vector;
- 1024-character vector keys;
- at most 10 nonFilterableMetadataKeys of 1 to 63 characters at
CreateIndex;
- 100 filter constraints per QueryVectors request.
A violation is a ValidationException before the engine is called.
* s3vectors: accept metadata whose JSON is exactly at the byte limits
metadataEntrySize counts a trailing comma for every member, so starting
from both braces overcounted by one and rejected metadata that encodes to
exactly 2 KB filterable or 100 KB total.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* s3vectors: rewrap the metadata limits header comment
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Chris Lu <chrislusf@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>