GILD verdict
Standardize on Amazon Bedrock when your organization runs on AWS and wants frontier and open models under its existing agreement and controls, as Zalando and Tines did for compliance and tenant residency.
Claude Opus 5.5 runs there on the Standard tier only, with no batch, Flex, Priority, Reserved or fast mode option as of Oct 28, 2026. Before production traffic, confirm each model's quota, its retention mode, and every API feature you need, and keep Anthropic's API as a second route the way DoorDash does.
Amazon Bedrock
AI Model API by Amazon Web Services
+9 MixedFit and limits
Who it fits
- Your organization runs on AWS, and a new model-vendor contract or security review would take months.
- You want Claude, OpenAI models, Amazon Nova, and open-weight models behind one IAM policy and one bill. One set of APIs includes the OpenAI-compatible Responses and Chat Completions APIs and Anthropic's Messages API.
- Data residency matters: Geo inference profiles keep current Claude models inside a geography such as the US or the EU, and inputs and outputs are not shared with model providers.
- You want managed building blocks: AgentCore to run agents from any framework, Knowledge Bases for retrieval, and Guardrails for content and PII filtering.
- You want a second route to the same Claude models: DoorDash falls back from the Claude API to Bedrock, and Fin serves Anthropic models through Bedrock, Vertex and Anthropic.
Where it falls short
- Claude in Amazon Bedrock lacks the Files API, Anthropic's server-side tools, the MCP connector, Message Batches, and Managed Agents. Structured outputs work there across the Claude model families, Opus 5.5 included.
- Batch is not listed for Claude Opus 5.5, Sonnet 5.5, Haiku 5.5, or Fable 5.1. Anthropic's 50% batch discount on its own API is not available for them on Bedrock. AWS's batch model table still ended at Claude Opus 5 on Oct 25, 2026.
- Quotas are set per model and per Region. Ziva's account got 5 requests per minute for Opus 4.6 against a 10,000 default and 16 days of escalation did not raise it (May 2026), and new accounts on r/aws report quotas of zero for every model.
- Opus 5.5 fast mode, which Anthropic's API and Foundry's Azure-hosted deployments sell at US$8 input and US$40 output, does not run on Bedrock (Oct 28, 2026).
- Claude Fable 5 failed with HTTP 400 on every message from Posit's Bedrock provider, whose requests ran in the default retention mode (Jul 2026); by Oct 23 the issue had not confirmed the cause.
- Bedrock Agents is now Agents Classic and closed to new customers; new agent work starts on AgentCore.
Implementation reality
Choose models and routing
Test two or three models through the inference profile you will use in production. Models run through the routing profile and Region you select. Compare Global and Geo rates for the chosen model, and check whether Geo or In-Region meets the workload's residency requirements. Verify the model's Standard row, supported tier, and cross-Region profile together before budgeting.
Plan capacity before launch
Request quotas per model and Region through Service Quotas, separately for on-demand and cross-Region inference. New accounts can start at zero: one re:Post user's quota page showed 0 tokens and requests per minute for every Claude model. AWS grants no increases for models scheduled for retirement. For steady traffic, Reserved offers 1 or 3 months of capacity from 100,000 input and 10,000 output tokens per minute. Provisioned Throughput sells Model Units by the hour.
Set the data retention mode
Set retention per Region at account or project level to none, default, aws_review, or legacy provider_data_share. Claude Fable 5 and 5.1 require aws_review. AWS keeps prompts and outputs for up to 30 days for review without sharing them with Anthropic. To enforce zero retention, set none through a Service Control Policy.
Attribute and cap spend
Attribute costs from the first workload using IAM principals, application inference profiles, or Projects. Track cache reads and writes per workload because each model publishes its own cache rates. Requesty's gateway saw 57% of Bedrock input tokens hit the cache in April 2026, against 77% on Anthropic's own API. Cost Explorer lists third-party model charges under the model provider. For agents, AgentCore Runtime v2 bills active CPU at US$0.1276 per vCPU-hour and memory at US$0.0169 per GB-hour, and CPU scales to zero while the agent waits on the model.
What to measure in your pilot
- Recheck the service tier table on each model card monthly. Until Batch shows a check, measure what share of each provider's workload could wait 24 hours and use the Bedrock batch row for that model.
- GILD found no account-team versus new-account approval times in AWS docs, re:Post, or practitioner posts; file increases four weeks before launch and escalate after five business days.
- Run one agent on AgentCore Runtime v2 and in your own container for two weeks and compare cost per session; if AgentCore costs more, keep it for burst traffic only.
Sources
- Official documentation
- 33
- Public source
- 4
- Amazon Bedrock User Guide: Overview
- Amazon Bedrock pricing
- AWS model card: Anthropic Claude Opus 5.5
- AWS model card: Amazon Nova Pro
- AWS model card: Meta Llama 4 Scout 17B
- AWS model card: Mistral Large 3
- AWS model card: DeepSeek V3.2
- AWS model card: OpenAI gpt-oss-120b
- AWS model card: Cohere Command R
- AWS model card: AI21 Jamba 1.5 Mini
- AWS price list: metered model rates
- AWS price list: foundation model rates
- Amazon Bedrock User Guide: Service tiers
- Amazon Bedrock User Guide: Batch inference
- Amazon Bedrock User Guide: Provisioned Throughput
- Amazon Bedrock User Guide: Cross-Region inference
- Amazon Bedrock User Guide: Global cross-Region inference
- Amazon Bedrock User Guide: Anthropic models
- Amazon Bedrock User Guide: Claude Opus 5.5 model card
- Amazon Bedrock User Guide: Structured outputs for Anthropic Claude models
- Amazon Bedrock User Guide: Claude Sonnet 5.5 model card
- Amazon Bedrock User Guide: Claude Fable 5.1 model card
- Amazon Bedrock User Guide: Data retention
- Amazon Bedrock User Guide: Abuse detection
- Amazon Bedrock FAQs
- Amazon Bedrock User Guide: Quotas for the bedrock-runtime endpoint
- Amazon Bedrock User Guide: Track usage and costs
- Amazon Bedrock User Guide: Agents
- Amazon Bedrock AgentCore
- Amazon Bedrock User Guide: Knowledge Bases
- Amazon Bedrock User Guide: Guardrails
- Amazon Bedrock AgentCore pricing
- Claude API docs: Claude in Amazon Bedrock (as of Oct 25, 2026)
- Amazon Bedrock User Guide: Supported Regions and models for batch inference
- Requesty: Operational metrics per provider, April 2026 (May 9, 2026)
- Requesty: Prompt-cache hit rate per provider, April 2026 (May 9, 2026)
- AWS re:Post: Bedrock returns Too many tokens per day for every Anthropic model on a new account (Jul 9, 2026)