Evaluate models through the routing profile you will use in production, get quota approved weeks before launch, and set retention and cost attribution before the first production request. Each step cites AWS documentation and public accounts from teams running Bedrock.
When you need this
Evaluation criteria
Setup: model access and permissions
Can the production role invoke every model you plan to use?
Look forGrant AWS Marketplace subscribe permissions to the calling role. Complete Anthropic's one-time use-case form on bedrock-runtime and test each model. Some models need account-level access through AWS Sales. One existing Claude customer got AccessDeniedException when adding GPT-5.6 Sol. Startups report zero frontier-model quotas on new accounts.
Model choice: evaluations on your task
Which model passes your own test set at the lowest cost per completed task?
Look forRun the same prompts on two or three models through the production routing profile. OutcomeOps found Haiku 4.5 gave the most complete answer among eight Bedrock models on retrieval. Another builder found only Claude handled a root-cause agent's tool calls. A client's document extraction matched Opus accuracy on Haiku at about a fifteenth of the cost.
Routing: Global or Geo
Does the workload have to stay inside a geography?
Look forChoose a routing profile that meets residency requirements, then compare the exact model prices for that profile. Claude Opus 5.5 is one example: Geo costs 10% more than Global and offers the US, EU, Australia, and Japan. Fable 5.1 offers only the US. On bedrock-runtime, Opus 5.5 has a single-Region endpoint only in London.
Capacity: quotas before launch
Is the tokens-per-minute quota approved for each model and Region you will call?
Look forFile requests through Service Quotas weeks before launch with expected traffic. Public accounts describe applied quotas far below documented defaults and increases taking weeks.
Cost control: caching and attribution
Does every workload report its cache hit rate and its own cost line?
Look forPut stable prompt prefixes behind explicit cache points and track reads per workload. Tag each feature with an application inference profile or Project. A US$37,901.73 bill and Codex cache ratios under 5% both began with silently failed caching.
Governance: retention per Region
Is the retention mode set in every Region you use?
Look forSet retention per Region at account or project level and enforce it with a Service Control Policy. Decide whether to permit models that require aws_review, currently Claude Fable 5 and 5.1.
Questions to ask vendors
- Which models on our roadmap lack a feature we need on Bedrock, such as batch or token counting?
- What is our approved tokens-per-minute quota for each model and Region, and how long did the last increase take?
- Which Region settings for data retention are still at inherit?
- Who reviews Bedrock spend by feature each week?
Red flags
- Launching on a model whose quota increase is still pending.
- Assuming a vendor API feature exists on Bedrock without checking the model card.
- One IAM role and no inference profiles, so cost cannot be traced to a feature.
- A timestamp or per-user content at the top of the prompt, ahead of the cached prefix.
Products in this piece
Sources
- Official documentation
- 7
- Public source
- 8
- Amazon Bedrock User Guide: Request access to models
- Amazon Bedrock User Guide: Claude Opus 5.5 model card
- Amazon Bedrock User Guide: Global cross-Region inference
- Amazon Bedrock User Guide: Quotas for the bedrock-runtime endpoint
- Amazon Bedrock User Guide: Prompt caching
- Amazon Bedrock User Guide: Track usage and costs
- Amazon Bedrock User Guide: Data retention
- r/aws: Cannot access OpenAI GPT-5.6 Sol in Bedrock (Sep 24, 2026)
- r/aws: New account with quota 0 on Bedrock frontier models (Aug 9, 2026)
- OutcomeOps: You're Probably Using the Wrong Bedrock Model (Apr 1, 2026)
- Hacker News comment testing a root-cause agent across Bedrock models (Apr 29, 2026)
- Ravindra Pandya: 5 Hard-Earned Lessons from Building a Production App on Amazon Bedrock (Jan 19, 2026)
- Ziva: 16 days, 4 channels, no AWS Bedrock quota fix (May 16, 2026)
- Hacker News: US$38k AWS Bedrock bill caused by a simple prompt caching miss (Apr 28, 2026)
- Hacker News comment on Codex cache writes on Bedrock (Aug 21, 2026)