AWS Builder Center
Choosing the Right Foundation Model in Amazon Bedrock: A Practical Guide for 2026

Choosing the Right Foundation Model in Amazon Bedrock: A Practical Guide for 2026

Amazon Bedrock provides access to more than 100 foundation models across text, reasoning, coding, image, video, audio and embedding workloads. This guide organizes the major model families by their core strengths and explains how to select the right model for a production use case.

Amazon Bedrock has evolved from a service offering a small selection of foundation models into a broad, multi-provider generative AI platform.
As of August 2026, Bedrock provides access to more than 100 models from providers including Amazon, Anthropic, OpenAI, Meta, Mistral AI, Cohere, DeepSeek, Google, xAI, NVIDIA, Moonshot AI, MiniMax, Stability AI, TwelveLabs, Writer and others.
Having more choices is valuable but it creates a new architecture question:
Which foundation model should I select for my workload?
The answer should not be based only on benchmark rankings. A production model must be evaluated across quality, latency, cost, modality, context size, regional availability, security requirements and compatibility with Amazon Bedrock capabilities.
This article organizes the major model families according to their areas of expertise and provides a practical selection framework.
The Bedrock catalog changes frequently, and model availability varies by AWS Region. Always confirm availability in the official  Amazon Bedrock model catalog .

1. General-purpose and reasoning models

These models support conversational AI, reasoning, content generation, document analysis and agentic workflows.
Provider
Major model families
Core strengths
Anthropic
Claude Opus, Sonnet, Haiku, Mythos and Fable families
Reasoning, coding, long documents, tool use and agents
OpenAI
GPT-5.6 Sol, Terra and Luna; gpt-oss
Frontier reasoning, coding, scientific analysis and scaled production inference
Amazon
Nova Premier, Pro, Lite and Micro
AWS-native multimodal intelligence across multiple cost and performance tiers
xAI
Grok family
Long-context reasoning, tool use and document-intensive workflows
DeepSeek
DeepSeek-R1 and V-series
Mathematical reasoning, coding and cost-efficient technical workloads
Moonshot AI
Kimi K2 family
Long-context analysis, coding, multimodal reasoning and multilingual work
MiniMax
M2 family
Very long context, multilingual processing and coding
Meta
Llama 4 and Llama 3 families
Open-model flexibility, general text and multimodal applications
Mistral AI
Mistral, Ministral, Magistral and Devstral families
Efficient multilingual reasoning and software development
Google
Gemma 4 and Gemma 3 families
Open multimodal reasoning across compact and larger model sizes
NVIDIA
Nemotron families
Efficient reasoning, coding and agent development
Writer
Palmyra families
Enterprise writing, business processes and document understanding

Premium reasoning

For difficult reasoning, software engineering, cybersecurity, research and multi-step agent workflows, evaluate models such as:
  • Claude Opus
  • Claude Sonnet
  • GPT-5.6 Sol
  • Grok
  • Kimi K2
  • DeepSeek-R1 or V-series
Premium models generally produce higher-quality results but may increase cost and latency.
They should be reserved for tasks where the additional reasoning quality creates measurable business value.

Balanced production workloads

Many enterprise applications do not require the most expensive model for every request.
Balanced models such as the following can offer a better combination of quality, latency and cost:
  • Claude Sonnet
  • GPT-5.6 Terra
  • Amazon Nova Pro
  • Mistral Large
  • Llama’s larger instruction models
These models are suitable for enterprise assistants, RAG applications, document processing and general agent workflows.

High-volume, cost-sensitive workloads

Smaller models are often better for:
  • Classification
  • Request routing
  • Entity extraction
  • Sentiment analysis
  • Basic summarization
  • Metadata generation
  • Simple question answering
Examples include:
  • Amazon Nova Micro
  • Amazon Nova Lite
  • GPT-5.6 Luna
  • Gemma compact models
  • Ministral
  • gpt-oss-20b
  • Smaller Llama and Nemotron variants
A common mistake is using a frontier reasoning model for every step of an application. A better architecture may use a small model for classification and routing, then call a larger model only when the request requires deeper reasoning.

2. Models for agentic AI

Agentic applications require more than text generation.
An effective agent model should be evaluated for:
  • Tool calling
  • Instruction following
  • Structured output
  • Multi-step reasoning
  • Context retention
  • Prompt caching
  • Response streaming
  • Compatibility with Bedrock Guardrails
  • Integration with Amazon Bedrock AgentCore
Strong candidates include:
  • Claude Sonnet and Opus
  • GPT-5.6 Sol and Terra
  • Amazon Nova Pro
  • Kimi K2
  • DeepSeek V-series
  • Grok
  • MiniMax M2
  • NVIDIA Nemotron
For sensitive workflows, the model should not be the only control. Use IAM, tool-level authorization, Bedrock Guardrails, application policies and human approval for high-impact actions.

3. Models for software development

Coding models should be tested using your organization’s actual repositories, languages and development practices.
Important evaluation areas include:
  • Code-generation accuracy
  • Repository-level understanding
  • Debugging
  • Refactoring
  • Test generation
  • Infrastructure as Code
  • Secure coding
  • Tool use
  • Following project-specific instructions
Models worth evaluating include:
Model family
Suitable workloads
Claude Sonnet
Repository analysis, coding agents, debugging and refactoring
GPT-5.6 Sol
Complex coding, cybersecurity and agentic engineering
Kimi K2
Long-context repository analysis and coding
DeepSeek
Coding and technical reasoning
Mistral Devstral
Software development and code understanding
gpt-oss
Open-model coding applications
Nemotron
Coding and tool-using agents
The best model for a Python application may not be the best model for C++, Terraform, Kubernetes or an organization-specific framework. Build an evaluation dataset from real engineering tasks.

4. Embedding models for RAG

Embedding models convert text or multimodal content into numerical vectors. They are commonly used for semantic search, recommendations and Retrieval-Augmented Generation.
Provider
Model families
Best suited for
Amazon
Titan Text Embeddings
Text-based semantic search and Bedrock Knowledge Bases
Amazon
Titan and Nova multimodal embeddings
Text-and-image retrieval
Cohere
Embed English, Multilingual and Embed v4
Multilingual and enterprise retrieval
TwelveLabs
Marengo Embed
Video, image, audio and text search

Selection guidance

  • Use Titan Text Embeddings for AWS-native, text-focused RAG.
  • Use Cohere Embed Multilingual when documents and questions span multiple languages.
  • Use Nova Multimodal Embeddings when users must retrieve information across text and images.
  • Use TwelveLabs Marengo when building video or media-search applications.
Embedding models cannot be replaced casually after production launch. Changing the model normally requires regenerating the existing vector index.
AWS notes that Marengo Embed 2.7 and 3.0 embeddings are not compatible. Applications migrating to 3.0 must regenerate their embeddings. Review the  Marengo migration guidance .

5. Reranking models

Vector search normally returns a set of potentially relevant documents. A reranker then reorders those documents based on their relevance to the user’s question.
Cohere Rerank models are available for this purpose.
A typical RAG workflow is:
User question ↓ Embedding model ↓ Vector database search ↓ Reranker ↓ Selected context ↓ Generative model
Reranking can improve answer quality when the vector database finds the correct document but does not consistently rank it first.

6. Image-generation models

Amazon Bedrock supports image-generation and specialized image-editing workloads.
Provider
Model families
Core areas
Amazon
Nova Canvas
Text-to-image generation and controlled image editing
Amazon
Titan Image Generator
Image generation, variation and customization
Stability AI
Stable Image models and services
Creative generation, editing, background removal, upscaling and style transfer
Use Nova Canvas or Titan Image Generator when AWS-native integration is important.
Stability AI is a strong option when the application requires specialized creative controls or image-transformation operations.

7. Video models

Bedrock supports both video generation and video understanding.

Video generation

  • Amazon Nova Reel
  • Luma AI Ray models
These models can support advertising, training, media and social-content workflows. Video generation normally uses asynchronous inference because it takes longer than a standard text request.

Video understanding

TwelveLabs offers models specialized for analyzing and searching video:
  • Pegasus generates summaries, descriptions and answers about video content.
  • Marengo creates multimodal embeddings for video search and retrieval.
Use Pegasus when you need to understand or summarize a video. Use Marengo when you need to search a large video collection.
AWS documents the available  TwelveLabs models in Amazon Bedrock .

8. Speech and audio models

Bedrock’s speech and audio catalog includes capabilities such as:
  • Real-time speech-to-speech interaction
  • Speech transcription
  • Audio understanding
  • Audio and video embeddings
Relevant families include Amazon Nova speech models, Mistral Voxtral and TwelveLabs Marengo.
Before selecting a voice model, verify its lifecycle. AWS currently identifies the original Nova Sonic release as a legacy model, so new architectures should confirm the recommended current model before adoption.

9. Open-model options

Organizations may prefer open-weight models for transparency, flexibility or alignment with an existing open-source strategy.
Bedrock includes models from families such as:
  • Meta Llama
  • Google Gemma
  • Mistral and Ministral
  • OpenAI gpt-oss
  • NVIDIA Nemotron
An open model is not automatically cheaper or easier to operate. Compare the managed Bedrock price, required customization, evaluation effort and operational requirements.

10. A practical model-selection framework

I recommend evaluating models across seven dimensions.

Quality

Does the model complete your organization’s actual tasks accurately?

Cost

Consider input tokens, output tokens, caching, provisioned throughput and the number of calls required to complete the workflow.

Latency

A model that provides the best answer in 30 seconds may not be suitable for an interactive customer-support application.

Context

Determine how much information the application really needs. A massive context window does not eliminate the need for good retrieval and context management.

Modality

Does the application require text, image, audio or video input? Does it need text, image, speech or video output?

Bedrock feature compatibility

Verify support for:
  • Converse API
  • Responses or Chat Completions APIs
  • Tool calling
  • Structured outputs
  • Guardrails
  • Knowledge Bases
  • Prompt caching
  • Model evaluation
  • Cross-Region inference

Governance and lifecycle

Confirm:
  • Regional availability
  • Data residency
  • Model-access requirements
  • Provider-specific data settings
  • Deprecation dates
  • Migration path
  • IAM and audit controls
The official  Amazon Bedrock model lifecycle page  should be part of every production review.

11. Suggested starting shortlist

Workload
Models to evaluate first
Premium reasoning
Claude Opus, GPT-5.6 Sol
Balanced enterprise applications
Claude Sonnet, GPT-5.6 Terra, Nova Pro
Cost-efficient processing
Nova Lite, Nova Micro, GPT-5.6 Luna, Gemma
Coding agent
Claude Sonnet, GPT-5.6 Sol, Kimi K2, DeepSeek
Open-model strategy
Llama, Gemma, Mistral, gpt-oss, Nemotron
Enterprise RAG
Claude/Nova/GPT + Titan or Cohere Embed + Cohere Rerank
Image generation
Nova Canvas, Titan Image Generator, Stability AI
Video generation
Nova Reel, Luma Ray
Video intelligence
TwelveLabs Pegasus and Marengo
Speech transcription
Mistral Voxtral and current Amazon speech models

12. Check the catalog programmatically

The following AWS CLI command returns the foundation models available through the Bedrock control-plane API in a selected Region:
aws bedrock list-foundation-models \
--region us-east-1 \
--query "modelSummaries[].{Provider:providerName,Model:modelName,ModelId:modelId,Input:inputModalities,Output:outputModalities}" \
--output table

Run it separately for every Region under consideration.
Some newer models may use different endpoints or access mechanisms and may not appear exactly as traditional Bedrock Runtime models. Confirm the individual model card and endpoint requirements before implementation.

Final takeaway

Amazon Bedrock gives architects access to a broad model ecosystem without requiring every model to be operated independently.
But access to more models does not remove the need for careful architecture.
The best model is not necessarily the one with the largest context window or the highest benchmark score. It is the model that delivers the required quality while meeting the application’s cost, latency, security, availability and governance requirements.
My preferred approach is simple:
  1. Define the workload.
  1. Select three candidate models.
  1. Evaluate them using real business data.
  1. Measure quality, latency and cost.
  1. Review security and regional requirements.
  1. Select the model based on evidence.
  1. Continue evaluating as the Bedrock catalog evolves.
In production generative AI, model selection should be an engineering decision not a popularity contest.

References

The opinions expressed in this article are my own and do not necessarily represent those of AWS or my employer.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article