Submit feedback on
Suboptimal Bedrock Model Type
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Suboptimal Bedrock Model Type
CER:
AWS-AI-4616
Service Category
AI
Cloud Provider
AWS
Service Name
AWS Bedrock
Inefficiency Type
Outdated Model Selection
Explanation

Bedrock’s model catalog evolves quickly as providers release new versions—such as successive Claude model families or updated Amazon Titan models. These newer models frequently offer improved performance, more efficient reasoning, better context handling, and higher-quality outputs compared to older generations. When workloads continue using older or deprecated models, they may require **more tokens**, experience **slower inference**, or miss out on accuracy improvements available in successor models. Because Bedrock bills per token or per inference unit, these inefficiencies can increase cost without adding value. Ensuring workloads align with the most suitable current-generation model improves both performance and cost-effectiveness.

Relevant Billing Model

Bedrock generally charges per input and output token (or per inference unit for certain model families). While newer models may not always have a lower price per token, they often deliver **better accuracy, faster responses, or reduced token requirements**, improving the effective cost-efficiency of the workload. Continuing to run older models can lead to higher spend for lower-quality output.

Detection
  • Identify Bedrock workloads still using older, legacy, or deprecated model versions
  • Assess whether similar results could be achieved with fewer tokens using newer model families
  • Evaluate latency, throughput, or output-quality gaps that may indicate inefficiency in older models
  • Review Bedrock’s model catalog, lifecycle status, or provider guidance to confirm if a recommended successor model exists
Remediation
  • Migrate workloads to the most current Bedrock model family that provides improved efficiency, accuracy, or throughput
  • Introduce periodic model reviews into platform or architecture governance to ensure ongoing modernization
  • Embed model lifecycle awareness into deployment processes so outdated models are identified and upgraded proactively
  • Validate functional compatibility and output quality after migration to ensure a smooth transition
Relevant Documentation
Submit Feedback