Vector search on S3, without a hosted vector database
You can keep your vectors in S3 and search them there. Three ways work today. AWS S3 Vectors stores embeddings in a special bucket type and answers similarity queries through an API. LanceDB writes a columnar vector format to any S3 path and queries it from your process. A vector store built on object storage, such as Mixpeek's MVS, keeps the index and payloads in your bucket and runs dense,…
You can store and search vectors directly in S3, without needing a hosted vector database. Three options are available today. AWS S3 Vectors handles embeddings in a special bucket type, answering similarity queries via an API. LanceDB writes columnar vectors to any S3 path and queries from your process. Mixpeek's MVS is a vector store built on object storage, keeping index and payloads in your bucket, and running dense, sparse, and BM25 search over them.
Factors to consider in switching include cold latency, hybrid search capabilities, query-time filters, and write paths. MVS, in particular, imports vectors from other vector stores like Pinecone, Qdrant, or Weaviate without re-embedding.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
