Skip to content

Vector DBAmazon Web Services

Amazon S3 Vectors

Native vector storage and querying in S3 — serverless, billion-vector scale.

Category
Vector DB
Pricing
PAID
Hosting
Cloud
Platforms
API
Models
Model-agnostic
Verified
Jun 11, 2026

Purpose-built vector storage inside Amazon S3: store and query up to two billion vectors per index across thousands of indexes per vector bucket, with S3's durability and elasticity and no clusters to manage. Frequent queries return in around 100ms and infrequent ones in under a second, and it plugs directly into Amazon Bedrock Knowledge Bases for RAG.

Capabilities 1

What it actually does — grouped by capability family.

  • Vector search (primary capability)

Pros & cons

  • Two billion vectors per index
  • S3 durability and elasticity
  • No idle compute costs
  • Native Bedrock Knowledge Bases integration
  • Locked to the AWS ecosystem
  • Cold queries are sub-second, not low-latency
  • Up to 100 results per query

Tags

Further reading

View all Vector DB
  • View Pinecone details
    Vector DBFREEMIUM

    Pinecone

    Pinecone

    Fully-managed serverless vector database for RAG and semantic search.

    Fully-managed vector DB built for production RAG and semantic search at scale. Serverless pricing, low-latency reads, and integrations across every major framework, with no infrastructure to provision or operate.

    No infra to provision or operate
    No self-host option
    • managed
    • serverless
    • rag
    • semantic-search
  • View Turbopuffer details
    Vector DBPAID

    Turbopuffer

    Turbopuffer

    Object-storage-backed vector DB. Serverless economics at scale.

    Bills like S3 — cold rest, warm reads, no per-namespace minimums. Designed for very-large, mostly-cold vector workloads where you can't justify keeping every index in RAM. Operated by Notion in production.

    S3-like billing: cold rest, warm reads
    Cold reads have higher latency
    • serverless
    • object-storage
    • cold-storage
    • scale
  • View LanceDB details
    Vector DBFREEMIUMOpen core

    LanceDB

    LanceDB

    Embedded multimodal vector database on the Lance format.

    An open-source retrieval engine for AI built on the Lance columnar format. It runs in-process alongside your app — no separate server — and stores, indexes, and searches vectors, metadata, and multimodal data (text, images, video) with vector, full-text, and SQL queries. A managed enterprise lakehouse tier scales the same engine to petabytes.

    Embeds in your app; runs on edge/desktop
    Newer; smaller community than Qdrant/Milvus
    • vector-search
    • multimodal
    • embedded
    • lance
    • +1
  • View Milvus details
    Vector DBFREEMIUMOpen core

    Milvus

    Zilliz

    Distributed vector database built for billion-scale search.

    Cloud-native, Apache-2.0 vector database for similarity search at scale, powering RAG, semantic and multimodal search, and recommendations. Its distributed architecture separates storage and compute and supports many index types (HNSW, IVF, FLAT, DiskANN, SCANN) with quantization and mmap. Created by Zilliz, which offers the managed Zilliz Cloud.

    Scales to billion-vector deployments
    Operationally heavy to self-host
    • vector-db
    • open-source
    • rag
    • ann-search
    • +1