Explanation
Why the waste happens and who it affects.
When workloads remain tied to older model versions, token consumption may increase, latency may be higher, and output quality may be lower. Using outdated models leads to avoidable operational costs, particularly for applications with consistent or high-volume inference activity. Regular modernization ensures applications take advantage of new model optimizations and pricing improvements.
Billing model
The pricing dimensions that drive this cost.
Bedrock Inference Profiles are billed based on model-specific rates per input and output token (or per request, depending on the model). Newer model versions can lower cost per task (for example, through fewer tokens or retries), but they are not always cheaper per token than the versions they replace. Legacy models in the public extended access period should expect higher pricing set by the model provider, and requests fail after the model reaches end-of-life.
How to detect
5 checks to find it in your estate.
- Review Bedrock Inference Profiles to identify deployments using older or deprecated model versions
- Check each model's lifecycle state (Active, Legacy, or EOL) in the console or the modelLifecycle field of GetFoundationModel, and flag Legacy models approaching public extended access or their EOL date
- Assess token usage trends to determine whether newer models could reduce cost-per-token for similar workloads
- Evaluate latency, performance, or quality issues that may be associated with older model versions
- Check AWS documentation for updated model recommendations or improved successor models
How to fix
4 ways to remove the waste.
- Migrate workloads to the most recent Bedrock model version that meets performance and cost goals
- Implement periodic review processes to ensure model selection stays aligned with AWS's latest model offerings
- Incorporate model lifecycle awareness into architecture standards so workloads modernize as new versions become available
- Validate application behavior and accuracy after transitioning to an updated model
Documentation
Vendor references for pricing and configuration.