Opportunity Name: Bedrock Model Route Optimization
AWS Resource Type: Amazon Bedrock
Opportunity Description:
This Finder identifies opportunities to reduce costs in Amazon Bedrock by analyzing your token usage and recommending one of two optimization paths: switching to a more cost-effective model within the same provider family, or enabling AWS Bedrock intelligent prompt routing so requests are automatically directed to the most cost-appropriate model.
CloudFix analyzes your Bedrock token usage (input and output tokens per model) and generates a report comparing your current model's cost against the recommended alternative.
Criteria for identifying the opportunity:
- High-frequency usage of a Bedrock model that has a lower-cost alternative within the same provider family (Path 1: Direct Model Switch).
- Eligibility for AWS Bedrock intelligent prompt routing (Path 2), which is currently supported only for
anthropic.claude-3-5-sonnet-20240620-v1:0andmeta.llama3-1-70b-instruct-v1:0, and only in the us-east-1 and us-west-2 regions.
This recommendation is based solely on cost. CloudFix does not evaluate latency, throughput, or output-quality differences between models — you should test the target model against your specific use case before switching.
Potential Savings (range in % on annual basis):
Savings depend on the usage volume and the cost delta between the current and recommended model. Direct model switches (Path 1) vary by the specific models involved; enabling intelligent prompt routing (Path 2) is estimated conservatively at around a 10% cost reduction, though real-world results can be higher.
What happens when the Fixer is executed?
This Finder does not include an automatic Fixer.
Model routing adjustments must be manually implemented by:
- Updating the application code or API configuration to use the alternative Bedrock model, or enabling intelligent prompt routing.
- Conducting a test run with the new model or routing configuration to validate performance and output quality.
- Deploying the updated configuration to production.
CloudFix provides a side-by-side comparison of token costs between your current model and the recommended alternative.
Is it possible to rollback once CloudFix implements the fixer?
Yes. Model routes can be reverted simply by restoring the original API configuration or redeploying the prior model integration.
Can CloudFix implement the fix automatically once I accept the recommendation?
No. Model route changes must be implemented manually by the customer.
Does this fix require downtime?
No. API configuration changes can be deployed without service interruption, assuming standard CI/CD and deployment practices are followed.
Additional Resources:
Bill Gleeson
Comments