Foundation Model (FM)
A pretrained model capable of performing general-purpose AI tasks and being adapted to different applications.
AIP-C01 · Study Guide
FM, Bedrock, RAG, embeddings, vector stores, retrieval, prompts, and resilience terms
A pretrained model capable of performing general-purpose AI tasks and being adapted to different applications.
AWS managed service for building generative AI applications using foundation models and related capabilities.
AWS service for building, training, customizing, deploying, and managing machine learning models.
Retrieval-Augmented Generation. A pattern where relevant external information is retrieved and supplied to the model as context before generation.
A numerical vector representation of content that captures semantic relationships.
A system used to store and retrieve vector representations efficiently.
Breaking documents into smaller retrievable units.
Additional information associated with a document or chunk, such as author, date, domain, or classification.
Searching for content based on vector similarity.
Searching based on lexical/exact terms.
Combining keyword and vector retrieval.
Reordering retrieved candidates according to a stronger relevance evaluation.
Adding related terms or concepts to improve retrieval.
Breaking a complex query into smaller subqueries.
A reusable prompt structure with variable inputs.
Managing reusable prompts, versions, and controlled prompt usage.
Controls designed to help enforce responsible and safe model interactions.
A workflow that orchestrates multiple prompt/model-related steps, including sequential and conditional processing.
An abstraction layer that decides which model should handle a request.
A resilience pattern that temporarily stops requests to a failing dependency.
Providing a reduced but usable service when the preferred AI capability is unavailable.
Low-Rank Adaptation, a parameter-efficient model adaptation technique.
A system for managing model versions and deployment lifecycle.
Checking that input data satisfies defined quality and schema requirements.
Transforming inconsistent data into a consistent representation.
Handling multiple data modalities such as text, image, and audio.
Proof of Concept. A limited implementation used to validate technical feasibility and business value.
AWS guidance for evaluating architectures across important design principles and operational concerns.
A Well-Architected Lens focused on considerations specific to generative AI workloads.
Agents, MCP, deployment, enterprise integration, FM APIs, streaming, resilience, and application tooling
Framework for building agentic applications where an agent can plan, use tools, and complete multi-step tasks.
Approach for coordinating multiple specialized agents that collaborate on different parts of a task.
Standardized way for an agent or model to interact with tools and external capabilities.
Tracking information about the current workflow or task, such as step, tool results, and next action.
Information retained across interactions or tasks, such as preferences and historical context.
Agent pattern that alternates between reasoning and acting with tools until a stopping condition is met.
Design pattern where humans approve, review, or intervene in high-risk or consequential agent actions.
Resilience pattern that temporarily stops calls to an unhealthy dependency instead of retrying endlessly.
Reserved Bedrock model capacity used when predictable throughput and latency are required.
Routing simpler requests to smaller models and escalating complex requests to larger or specialized models.
Abstraction layer that centralizes model access, routing, auth, and policy for enterprise GenAI applications.
Returning model output incrementally as tokens are generated, often via WebSockets or Server-Sent Events.
Retry strategy that increases wait time between attempts to avoid overwhelming a failing dependency.
Selecting which foundation model handles a request based on rules, request characteristics, or metrics.
AWS infrastructure deployed closer to or in on-premises environments for low-latency or data-residency needs.
AWS edge infrastructure for ultra-low-latency workloads, often associated with 5G applications.
AWS developer assistant used to improve productivity for coding, diagnosis, and suggested fixes.
Distributed tracing service used to follow a request across service boundaries and locate latency or failures.
Bedrock capability for visual or declarative orchestration of multi-step model workflows.
IAM principle of granting only the minimum permissions required for an agent, tool, or service to operate.
Guardrails, PII, PrivateLink, Model Cards, invocation logging, Clarify, and responsible AI
Runtime safety controls that filter inputs and outputs using content filters, denied topics, word filters, PII actions, prompt-attack filters, and contextual grounding checks.
Guardrails evaluation of the incoming prompt before the foundation model is invoked.
Guardrails evaluation of the model completion before it is returned to the client.
Natural-language topic definitions that Guardrails blocks across supported models without changing prompts or weights.
Guardrails capability that compares a candidate completion to retrieved source reference passages to detect ungrounded hallucinations.
PII handling mode that replaces sensitive values with placeholders such as [NAME] or [EMAIL] while allowing the request to continue.
PII handling mode that rejects the request when configured sensitive entities are detected.
Private network path for Bedrock API calls so traffic stays on the AWS backbone instead of the public internet.
Customer-controlled encryption key used for data at rest across Bedrock-related stores such as S3, Knowledge Bases, and OpenSearch.
Service that discovers sensitive data such as PII in S3 before indexing into RAG corpora.
Standardized documentation of model provenance, training data, metrics, and intended usage boundaries for audits.
Opt-in logging of Bedrock request payloads, completions, and metadata to CloudWatch Logs or encrypted S3.
Central metadata catalog for training and RAG datasets used for lineage and schema tracking.
Fine-grained access control over data lakes, often paired with Glue Data Catalog for AI dataset governance.
Bias and fairness evaluation and continuous monitoring for model endpoints.
Step-by-step visibility into agent reasoning paths such as Rationale, Action, and Observation.
Guardrails filter that detects attempts to override instructions or exfiltrate system prompts.
Token cost, cascading, Prompt Caching, Batch Inference, streaming, and GenAI observability
Reducing prompt fluff and retaining only critical semantic content to lower input token cost.
Routing simple queries to cheap/fast models and escalating complex queries to higher-capability models.
Asynchronous Bedrock execution for non-real-time jobs, typically ~50% cheaper than on-demand calls.
Caches pre-computed KV activation states for long static prompt segments to cut repeated input token charges and latency.
Returning a stored answer when a new query is highly similar to a prior one, avoiding a new FM invocation.
Latency until the first generated token reaches the user; improved by streaming.
Bedrock streaming APIs that emit tokens incrementally for WebSocket or SSE delivery.
Decoding parameter controlling randomness; near 0.0 for deterministic math/code, higher for creative tasks.
Decoding controls that limit sampling to a nucleus of high-probability tokens.
Restricting vector search candidates by metadata before distance calculations to improve retrieval latency.
Approximate nearest-neighbor indexing used to accelerate vector similarity search.
CloudWatch/Bedrock metrics used to track token consumption for cost and capacity analysis.
Reserved Bedrock capacity for sustained high-volume traffic with strict latency SLAs.
LLM-as-a-Judge, quality gates, truncation diagnostics, Hybrid Search, and agent IAM troubleshooting
Lexical n-gram overlap metrics; useful for basic summary matching but weak for factual correctness.
Embedding-based semantic similarity between generated text and reference answers.
Using a stronger foundation model to score candidate responses against defined quality rubrics.
Whether every claim in a completion is supported by retrieved context.
Whether the completion directly addresses the user prompt without tangential bloat.
Whether retrieval pulled needed facts without excess noise.
Evaluating A vs B and B vs A, then averaging, to neutralize LLM judge position bias.
Managed evaluation jobs with Automated or Human Evaluation workflows for model/prompt comparison.
CI/CD check that blocks promotion when faithfulness, truncation, or other scores miss thresholds.
Completion stopped because the configured output token limit was hit; fix by raising maxTokens.
Pre-generation failure when prompt+context exceed the model context window; fix by chunking/compressing input.
Combining BM25 keyword matching with dense vector search, often plus reranking, for exact codes and semantic matches.
API/job that syncs Bedrock Knowledge Bases with source data (e.g., S3) after uploads or updates.
IAM permission the Bedrock Agent execution role needs to call tool Lambdas; missing it yields AccessDeniedException.