Study guide
2.4 Embedding Models & Vector Representations
AWS Certified Generative AI Developer - Professional AIP-C01
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Foundation Model Fundamentals
1.1 AIP-C01 Exam Structure, Logistics & Passing Strategy 1.2 AIP-C01 Scoring & Professional Decision Strategy 1.3 Foundation Model Landscape & Model Selection on Amazon Bedrock 1.4 Model Abstraction, Controlled Switching & Resilience 1.5 Customization Spectrum: Prompting vs RAG vs Fine-Tuning vs Continued Pre-training 1.6 Custom Model Deployment & Lifecycle Management
2 Chapter 2: Bedrock Knowledge Bases & RAG Architectures
2.1 Managed RAG Architecture with Bedrock Knowledge Bases 2.2 Knowledge Source Integration, Synchronization & Freshness 2.3 Data Ingestion, Parsing & Chunking Strategies 2.4 Embedding Models & Vector Representations 2.5 Vector Index Scale, Migration & Retrieval Evaluation 2.6 Vector Database Selection: OpenSearch Serverless vs Aurora pgvector vs Managed Stores 2.7 Vector Store Security, Multi-Tenancy & Connectivity
3 Chapter 3: Advanced Vector Search, Indexing & Data Compliance
3.1 Hybrid Search, Metadata Filtering & Semantic Reranking 3.2 Metadata Filtering, Reranking & Query Transformation 3.3 Fine-Tuning & Continued Pre-Training Data Pipeline Engineering 3.4 Data Validation, Multimodal Processing & Model Formatting 3.5 Data Privacy, Data Residency & Compliance Governance 3.6 Privacy Preservation, Source Lineage & Audit Evidence
4 Chapter 4: Prompt Engineering & Bedrock Runtime APIs
4.1 Advanced Prompt Engineering Techniques & Inference Parameters 4.2 Inference Parameters, Prompt Governance & Regression 4.3 Converse API vs InvokeModel API & Message Formatting 4.4 Tool Calling, FM API Resilience & Model Routing 4.5 Streaming Architectures & Asynchronous Event Processing 4.6 Resilient Streaming, Deployment & Asynchronous Processing
5 Chapter 5: Amazon Bedrock Agents & Tool Integration
5.1 Agentic Architecture, ReAct Reasoning Loops & Orchestration 5.2 Agent Frameworks, MCP & Lifecycle Management 5.3 Action Groups, OpenAPI Schemas & AWS Lambda Integration 5.4 Agent Memory, Session State & Multi-Agent Collaboration Patterns 5.5 Persistent State & Multi-Agent Coordination 5.6 Advanced Agent Prompt Templates & Flow Customization 5.7 Agent Safeguards, Tool Reliability & Cost Control
6 Chapter 6: Workflow Orchestration & Application Integration
6.1 Amazon Bedrock Prompt Flows & Visual Orchestration 6.2 Step Functions Orchestration & Human-in-the-Loop Workflows 6.3 Enterprise Integration: API Gateway, AppSync, and EventBridge 6.4 Hybrid Integration, GenAI Gateways & CI/CD Tooling
7 Chapter 7: AI Safety & Guardrails for Amazon Bedrock
7.1 Guardrails Architecture, Denied Topics & Content Filters 7.2 Content Safety, Defense in Depth & Threat Detection 7.3 Sensitive Information Filters & PII Redaction/Masking 7.4 Contextual Grounding Checks & Hallucination Prevention
8 Chapter 8: Security, Access Control & Network Architecture
8.1 IAM Least Privilege & Resource Policies for Bedrock 8.2 PrivateLink VPC Endpoints & Network Isolation 8.3 Encryption with AWS KMS & Cross-Account Access Patterns
9 Chapter 9: Governance, Auditing & Operational Logging
9.1 SageMaker Model Cards & AI Governance Frameworks 9.2 Lineage, Fairness, Transparency & Continuous Governance 9.3 Invocation Logging, CloudTrail Auditing & Observability 9.4 Responsible AI, Bias Mitigation & Red Teaming Methodologies
10 Chapter 10: Performance, Throughput & Cost Optimization
10.1 On-Demand vs Provisioned Throughput & Capacity Planning 10.2 Capacity Measurement, Scaling Patterns & Resilience 10.3 Batch Inference & Bedrock Intelligent Prompt Routing 10.4 Intelligent Prompt Routing & Application Eligibility 10.5 Prompt Caching, Token Optimization & Latency Reduction
11 Chapter 11: Testing, Evaluation & Troubleshooting GenAI Solutions
11.1 Amazon Bedrock Model Evaluation (Automatic & Human Workflows) 11.2 Human, RAG & Continuous Evaluation 11.3 Evaluation Metrics & RAG Quality Benchmarking (Ragas, ROUGE, BLEU) 11.4 RAG and Agent Performance Evaluation 11.5 CloudWatch Metrics, Throttling & Operational Observability 11.6 Quota Diagnosis, Retry Control & Operational Troubleshooting 11.7 Troubleshooting Common GenAI Failure Modes & Agent Traces 11.8 Prompt Maintenance, Content Handling & Deployment Validation
2.4 Embedding Models & Vector Representations
Key Takeaways Explain This Topic AI
Benchmark dimensions and embedding models on labeled domain queries before migrating an index.
Unit-normalized vectors make dot-product and cosine rankings equivalent, but normalization must be verified.
Apply authorization metadata before retrieval results reach the model and keep metadata synchronized with source changes.
Last updated: September 2026
2.4 Embedding Models & Vector Representations
An embedding model maps content into a numeric vector so semantically related items can be found by distance. Retrieval quality depends on the complete contract among the embedding model, input preparation, vector dimensions, distance metric, index, metadata, and evaluation set. A dimension count by itself does not prove quality.
Select an embedding model from workload evidence
Check the exact model documentation for supported languages, modalities, maximum input size, output dimensions, normalization options, and Region availability. Text-only models cannot directly represent image content. Multilingual support should be tested with the organization's actual language pairs, not inferred from an English benchmark. If a provider uses asymmetric embeddings, encode corpus passages with the document input type and queries with the query input type.
Amazon Titan Text Embeddings V2 supports configurable output dimensions. Lower dimensions reduce raw vector storage and arithmetic, but there is no universal percentage of quality retained for every corpus. AWS service-card benchmark values are aggregate results, not a promise that a particular 512-dimension index will preserve a fixed percentage of a 1024-dimension index's recall. Benchmark the candidate dimensions against labeled queries and acceptance thresholds.
Distance and normalization
Cosine similarity compares direction, dot product compares the inner product, and Euclidean distance compares geometric separation. When both vectors are normalized to unit length, ranking by dot product is equivalent to ranking by cosine similarity. This mathematical fact does not mean every service normalizes automatically. Confirm the model output and index configuration.
Choice Benefit Risk to test
Fewer dimensions Lower vector storage and faster comparisons Lost distinctions and lower recall on domain terms
- Normalized vectors Stable cosine or dot-product behavior Incorrect assumptions if only one side is normalized
- Approximate nearest neighbor index Low-latency search at scale Recall varies with graph or probe parameters
- Exact search Useful ground truth for smaller evaluation sets Cost and latency grow with corpus size
Raw storage is approximately record count multiplied by dimensions multiplied by bytes per value, but a production index also stores graph edges, document text, metadata, replicas, and engine overhead. Capacity planning should measure the actual index rather than multiplying vectors alone.
Metadata is part of retrieval design
Metadata improves precision and enforces query constraints that semantic distance cannot express. Useful fields include tenant ID, source type, jurisdiction, effective date, product, language, and access group. Define types consistently: a year stored sometimes as text and sometimes as a number produces unreliable filters. Avoid high-cardinality or oversized fields that the selected store handles poorly.
Apply authorization filters before results reach the model. Post-filtering a globally retrieved top-k list can leak metadata and can return no useful passages even when authorized matches exist lower in the ranking. For especially sensitive tenants, physical or logical index separation may be required in addition to filters.
Metadata has a lifecycle. When a policy changes jurisdiction or a user's access group changes, stale attributes can make an otherwise current embedding unsafe. Synchronization must update vectors, text, and metadata as one governed record.
Worked dimension comparison
For ten million float32 vectors, raw vector values alone require about 40.96 GB at 1,024 dimensions and 20.48 GB at 512 dimensions. That arithmetic excludes graph edges, text, metadata, replicas, and engine overhead, so it is a lower bound rather than a cluster-size recommendation.
Create a labeled set of real queries, relevant documents, and hard negatives. Build parallel indices at both dimensions with the same corpus and measure recall at k, mean reciprocal rank, p95 query latency, build time, and total storage. Slice results by language and document type. If 512 dimensions meets every threshold, the savings are supported by evidence; if a rare but critical class loses recall, the aggregate average is insufficient.
Document the chosen embedding model ID and preprocessing. Even dimensions with the same number are not compatible across different models. Mixing their vectors in one field destroys geometric meaning.
Input preparation controls
Chunk content before embedding according to its semantic structure and the embedding model's input limit. Preserve headings and source identifiers, normalize encoding, and avoid silently truncating the decisive sentence. Generate document and query vectors with the same compatible model version and preprocessing contract, except for documented asymmetric input roles.
A final selection report should name the corpus snapshot, query set, relevance judgments, index settings, hardware or managed capacity, and confidence limits. Without these details, a retrieval score cannot be reproduced after a model or engine update.