# How to cut your AWS Bedrock costs

Bedrock spend hides inside the AWS bill, which makes attribution the first problem and model choice the second. In order:

## Playbook (in order of leverage)

1. **Cost attribution & AI FinOps** — Enable model-invocation logging and tag by application inference profile — untagged Bedrock spend is invisible in Cost Explorer. (https://cutmyaispend.com/methods/cost-attribution-finops.md)
2. **Model routing & cascades** — Nova Micro/Lite are among the cheapest capable models anywhere; route simple tasks there before touching Claude-on-Bedrock pricing. (https://cutmyaispend.com/methods/model-routing.md)
3. **Prompt caching** — Bedrock supports prompt caching for Claude and Nova models — same stable-prefix discipline applies. (https://cutmyaispend.com/methods/prompt-caching.md)
4. **Batch APIs** — Bedrock batch inference is ~50% off for async jobs. (https://cutmyaispend.com/methods/batch-apis.md)
5. **Cheaper & open models / self-hosting** — Provisioned throughput only pays off at sustained high volume — price it against on-demand honestly before committing. (https://cutmyaispend.com/methods/cheaper-and-open-models.md)

**Pro tip:** Watch account-level quotas (RPM throttles) — teams often upgrade to bigger models to “fix” throttling that a quota request would solve for free.

---
Canonical: https://cutmyaispend.com/providers/aws-bedrock