AWS Bedrock cost tracking
Every Bedrock model, split out of the rest of your AWS bill.
How does Camaze work with AWS Bedrock?
Camaze connects to AWS Bedrock with read-only credentials and pulls spend and usage into the same view as every other place you pay for AI.
What Camaze pulls from AWS Bedrock
Bedrock charges arrive inside the AWS bill, mixed with every other AWS service and often spread across several accounts. Camaze isolates Bedrock spend, splits it by model and by account, and reports provisioned throughput separately from on-demand so unused reserved capacity is visible.
- Total spend, by billing period
- Usage by model, including input, output and cached tokens
- Cost by API key, project or workspace
- Rate of change, so a jump is visible the day it happens
See your AWS Bedrock spend in context.
Book a walkthrough and we will show you AWS Bedrock costs next to everything else you pay for AI.
Keep reading
Every integration
The full list of providers, tools, self-hosted sources and destinations Camaze connects to.
Read moreSpend visibility
How AWS Bedrock spend joins every other source on one cost basis, in one number.
Read moreCost optimization
The standing list of what to cut, including findings specific to AWS Bedrock usage.
Read moreQuestions people ask
What access does Camaze need for AWS Bedrock?
Read-only billing and usage credentials. Nothing that can spend money, change a deployment, or read your prompts and completions. Details are on the security page.
Does it backfill historical AWS Bedrock spend?
Yes. Camaze pulls the available history on connection, typically the last twelve months, so you start with a trend rather than an empty chart.
Can we split AWS Bedrock spend by team or project?
Yes. Map keys, projects, workspaces or tags to your own org structure once, and every AWS Bedrock charge is attributed from then on. See cost allocation.
Do we have to use AWS Bedrock exclusively?
No. Camaze is built for the opposite case. AWS Bedrock sits alongside every other provider, tool and self-hosted model in the same view, on the same cost basis. It is equally useful if AWS Bedrock is the only thing you run: see single-provider visibility.