Amazon Bedrock+9 Mixed

GILD Review

GILD's call and the buying facts behind it.

From GILD research

Should we adopt Amazon Bedrock?

What do you give up by buying models through Amazon Bedrock and skipping each vendor's own API?

30-Second TakePick Amazon Bedrock if you want several providers' models under the AWS agreement and controls you already have.
Best fitTeams on AWS buying models from several providers under one agreement, with data kept inside their AWS boundary.GILD Review
Consider another workflowIf you need a vendor's newest API features on day one, such as Claude's Message Batches or server tools, buy from the vendor or through Claude Platform on AWS.GILD Review

Drawn from 169 sources and 13 operator insights

GILD analysis

Amazon Bedrock Review

Amazon Bedrock makes a team wait twice, once for quota approvals per model and Region and again for API features that reach vendors' own platforms first. In return, teams get models from many providers on AWS billing, inside the account's IAM controls and Regions, and DoorDash and Fin run it beside Anthropic's API as a second route to the same Claude models. Global routing follows each provider's listed model price, while other modes change price or capacity.

AI Model APIs
AI Costs

The decision

Best fit: Teams on AWS buying models from several providers under one agreement, with data kept inside their AWS boundary.
Consider another workflow: If you need a vendor's newest API features on day one, such as Claude's Message Batches or server tools, buy from the vendor or through Claude Platform on AWS.
Adoption condition: Confirm quotas for each model and Region. Set a data retention mode per Region. Finish both before production traffic.

Basis: AWS documentation, pricing, data terms, and model cards, and 149 public accounts, including DoorDash's InfoQ talk and 15 r/aws posts. These include an Artificial Analysis provider benchmark where Bedrock led Claude Sonnet 5 output speed at 85.9 tokens per second. Requesty's gateway measured about 96% request success on both Bedrock and Anthropic's own API in April 2026.

Buying & deployment factsWhat a team building on it should verify before production traffic grows.

How you buy it

Per-model usage

AWS bills each model's tokens. Compare the vendor's model row and the pricing mode.

Source 1, Amazon Web Services, Pricing: Pricing Source 2, Amazon Web Services, Service tiers: Service tiers Source 4, Amazon Web Services, Claude Opus 5.5 model card: Claude Opus 5.5 model card Source 6, b0.p.awsstatic.com, AWS price list feed: third-party models: AWS price list feed: third-party models Source 7, b0.p.awsstatic.com, AWS price list feed: Amazon and open-weight models: AWS price list feed: Amazon and open-weight models

Details

Standard on-demand bills each model's input and output tokens through AWS, with no commitment. Batch is 50% below on-demand for supported models, while Flex is 50% below Standard and Priority is 75% above it. Reserved tier and Provisioned Throughput trade a commitment for capacity. AWS bills third-party models such as Claude through AWS Marketplace, listed under the model provider on your AWS bill. Verify the model row and tier before budgeting.

Representative Standard on-demand rates, US dollars per 1M tokens. US East (N. Virginia), except Claude on Global routing.
Model	Input	Output
Anthropic Claude Opus 5.5 (Global)	4.00	20.00
Amazon Nova Pro	0.80	3.20
Meta Llama 4 Scout 17B	0.17	0.66
Mistral Large 3	0.50	1.50
DeepSeek V3.2	0.62	1.85
OpenAI gpt-oss-120b	0.15	0.60
Cohere Command R	0.50	1.50
AI21 Jamba 1.5 Mini	0.20	0.40

AWS model pricing

Cost drivers

Model-specific rates

Tokens, routing geography, cache reads and writes, and pricing mode set the bill.

Source 1, Amazon Web Services, Pricing: Pricing Source 4, Amazon Web Services, Claude Opus 5.5 model card: Claude Opus 5.5 model card

Details

Model choice, input and output tokens, routing geography, cache reads and writes, and the pricing mode set the bill. Batch, Flex, Priority, Reserved, Provisioned Throughput, cross-Region inference, and prompt caching are separate choices with model-specific support.

Where it runs

Your AWS account

Under IAM, PrivateLink, and CloudTrail. Routing profiles vary by model and Region.

Source 4, Amazon Web Services, Claude Opus 5.5 model card: Claude Opus 5.5 model card Source 5, docs.aws.amazon.com, Data protection: Data protection

Details

Bedrock runs in AWS Regions through bedrock-runtime and bedrock-mantle under the account's IAM, PrivateLink, and CloudTrail. Models can use Global, cross-Region, Geo, or In-Region profiles where AWS lists them; availability and price vary by model and Region. Claude Opus 5.5 uses Global or Geo profiles for the US, EU, Australia, or Japan, and on bedrock-runtime it also runs In-Region in London.

What to verify

Quotas and retention

Check each model and Region. Claude Fable's aws_review retains traffic for up to 30 days.

Source 3, Amazon Web Services, Data retention: Data retention Source 4, Amazon Web Services, Claude Opus 5.5 model card: Claude Opus 5.5 model card Source 8, Anthropic, Claude features overview (Anthropic): Claude features overview (Anthropic)

Details

Default quotas apply per account and vary by Region. Retention is set per Region and also depends on the model. Claude Fable 5 and 5.1 require aws_review, which keeps prompts and completions up to 30 days inside AWS. Bedrock lacks some vendor API features for Claude, including Message Batches and most server tools: Opus 5.5 runs only the tool search server tool, in its regex and BM25 forms. On bedrock-runtime, Claude Opus 5.5 supports structured outputs and lacks token counting.