A vector database stores embeddings, the lists of numbers that capture what a piece of text or an image means, and finds the stored items closest in meaning to a query. Every RAG application needs one. AWS offers several services that can play this role, and the exam expects you to pick the one that fits a scenario's existing data, skills and query needs.
What a Vector Store Does
A vector store keeps each embedding together with its original text and some metadata, such as the source file and date. When a query arrives, it is embedded too, and the store runs a similarity search, often called k-nearest neighbor (k-NN) search, to return the closest matches. Good vector stores also let you filter by metadata, for example "only documents from the HR folder".
Amazon OpenSearch Service
OpenSearch is a search and analytics service that supports vector search alongside full-text keyword search, filters and aggregations. Two deployment styles matter:
- OpenSearch Serverless vector search collections: you don't manage any cluster; capacity scales with the workload. A common default for new RAG projects.
- OpenSearch Service managed clusters: you size and run the domain yourself, for teams that already operate OpenSearch.
Choose OpenSearch when vector search must combine with keyword search, rich filtering, or large scale.
Aurora and RDS for PostgreSQL with pgvector
pgvector is an open-source PostgreSQL extension that adds a vector data type and similarity search. It's available in both Amazon Aurora PostgreSQL-Compatible Edition and Amazon RDS for PostgreSQL. This lets a team keep embeddings in the same relational database as its business data and query both with SQL. Aurora PostgreSQL is also a supported vector store for Amazon Bedrock Knowledge Bases.
Choose this route when the company already runs PostgreSQL, has SQL skills, or wants vectors joined with relational records.
Amazon Neptune Analytics
Neptune is AWS's graph database family. Neptune Analytics graphs can hold a vector index, and Amazon Bedrock Knowledge Bases uses them for GraphRAG. GraphRAG first finds relevant chunks by vector search, then follows the relationships between entities in a graph to gather connected facts. That helps when answering a question means linking facts spread across several documents, for example which products contain a part from a supplier named in a recall notice.
Choosing a Store
| Scenario clue | Likely choice |
|---|---|
| New RAG project, no servers to manage | OpenSearch Serverless vector search collection |
| Vector search plus keyword search and filters | Amazon OpenSearch Service |
| Data and skills already in PostgreSQL | Aurora or RDS for PostgreSQL with pgvector |
| Answers need relationships across documents | Neptune Analytics (GraphRAG) |
Amazon Bedrock Knowledge Bases can also connect to other supported stores, including Amazon S3 Vectors and some third-party databases. Its quick-create option can set up a vector store for you.
On the Exam
Look for what the company already has or needs. "Already uses PostgreSQL" points to pgvector. "Serverless" or "keyword plus semantic search" points to OpenSearch. "Relationships", "connected facts" or "graph" points to Neptune. A plain key-value database with no vector search is a common wrong answer.