Connector docs — Amazon Bedrock
Exactly what CostMon asks for to read Amazon Bedrock
CostMon joins AWS Cost Explorer's Bedrock spend with CloudWatch's per-model token metrics, using the same read-only, cost-scoped pattern as the AWS connector.
What CostMon calls
The literal API surface, nothing more
- Cost Explorer — GetCostAndUsage
- Bedrock usage-type spend, parsed back into model IDs.
- CloudWatch — ListMetrics + GetMetricData
- Per-model input/output token counts and invocation counts, same day granularity.
What you supply
Credential and config fields
access_key_idAccess key IDsecretrequired
secret_access_keySecret access keysecretrequired
session_tokenSession tokensecretoptional
regionRegionoptional
assume_role_arnAssume role ARNoptional
days_backDays backoptional
Minimum permission
Copy this, not a broader role
Scope of access
What Amazon Bedrock access can't reach
- Prompts, completions, or any model input/output content
- Bedrock model configuration or provisioned throughput settings
Worth knowing
- Token counts require the AWS/Bedrock CloudWatch metrics to be enabled. If they're absent, rows sync as cost-only. The sync never fails for it, you just lose the per-model breakdown.
FAQ
Common questions about the Amazon Bedrock connector
What happens if CloudWatch metrics aren't enabled for Bedrock?
Cost still syncs from Cost Explorer. You lose the per-model token breakdown, not the cost data. The connector degrades gracefully rather than failing.
Is this the same AWS credential as the plain AWS connector?
It's the same shape (access key, secret, optional session token) but a separate connector with its own credentials, scoped to Cost Explorer plus the two CloudWatch read actions above.
A rate you looked up will change again.
Provider pricing pages change without notice. CostMon tracks the bill that pays for it.