# Amazon — Four Amazon Bedrock inference choices that affect cost

- Company: Amazon (amazon.com)
- Announced: 2026-11-12T20:51:55+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/four-amazon-bedrock-inference-choices-that-affect-cost/
- Record: https://forck.live/items/35548-four-amazon-bedrock-inference-choices-that-affect-cost
- Subject: Bedrock / Nova
- Models affected: Anthropic Claude Sonnet 5, Anthropic Claude Opus 5, Amazon Nova 2 Lite, OpenAI gpt-oss-120b
- Pricing: For Anthropic Claude Sonnet 5 and Anthropic Claude Opus 5 on Amazon Bedrock, a 5-minute write costs 1.25 times the input rate. A 1-hour write costs 2 times, and a cache read costs 0.1 times.

Amazon's guide explains four request-level Amazon Bedrock settings that change inference cost without changing the model or prompt: cache duration, service tier, reasoning effort, and maxTokens. Every Bedrock response carries usage metadata, and input and output tokens bill at the rate for the model and tier that served the request, with cache reads and writes on separate counters and reasoning tokens counted as output. For Anthropic Claude Sonnet 5 and Anthropic Claude Opus 5 on Bedrock, a 5-minute cache write costs 1.25 times the input rate, a 1-hour write costs 2 times, and a cache read costs 0.1 times, which sets the break-even between the two durations. A 5-minute cache pays back on the first reuse within 5 minutes, while the 1-hour cache is cheaper from the second request within the hour when the same prefix recurs more than 5 minutes apart. Flex is a service tier for latency-tolerant work such as background jobs and nightly summarization; the Amazon Nova 2 Lite and OpenAI gpt-oss-120b model cards list it as supported, while the cards for Claude Sonnet 5 and Claude Opus 5 list it as not supported. A Flex request to an unsupported model fails with a ValidationException rather than silently running on Standard, and Amazon says applications should catch that error and retry once with default rather than retrying every ValidationException.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/four-amazon-bedrock-inference-choices-that-affect-cost/:

> Your Amazon Bedrock inference bill can keep climbing after you tune prompts and application logic. Request-level choices can still change how many tokens the service processes and the rate applied to them. Cache duration, service tier, reasoning effort, and maxTokens can affect cost without changing your model or prompt.
> 
> Each choice depends on the model and workload. This post shows how we tested each choice and how to verify its effect from response metadata, logs, and billing data.
> 
> To try these settings yourself, start with the Amazon Bedrock Samples notebooks Mixed TTL Caching and Tenant Isolation with Prompt Caching . For maxTokens and reasoning effort, see the 01-low-effort folder of the sample-code-for-genai-cost-management-workshop GitHub repo. Each sample sets its own model ID, so change it, and the inference parameters, to match the model you call. For model availability by AWS Region, refer to Models at a glance . For broader decisions such as model selection, batch inference, routing, and distillation, see Effective cost optimization strategies for Amazon Bedrock .
> 
> Where inference cost comes from
> 
> Every Amazon Bedrock response carries usage metadata.

---

Record: https://forck.live/items/35548-four-amazon-bedrock-inference-choices-that-affect-cost
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
