Bedrock Cost Attribution & AI Spend Analytics
Waltsoft Inc. · Intelligence & Research
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
AWS Cost and Usage Reports show Bedrock costs per IAM principal - but with a 24-48 hour delay and require CUR exports, Athena queries, and manual configuration.
Bedrock Cost Attribution gives you the same data in MINUTES. Deploy in 5 minutes. See costs within minutes of them happening - not days later.
Show the rest of the publisher’s description (25 more lines)
Why Bedrock Cost Attribution vs native AWS tools:
- Near-real-time attribution (minutes via invocation logging, not 24-48 hours)
- One-click dashboard (no CUR exports, no Athena, no SQL)
- MCP Server for AI agents to query cost data programmatically
- Daily email digest with top spenders and trends
- Spend spike alerts via SNS (catch runaway costs immediately)
- 5-minute CloudFormation deploy (vs hours of CUR and Athena setup)
How it works:
- Subscribe and deploy CloudFormation template in your account
- Enable Bedrock Model Invocation Logging (one-time setup - see below)
- Lambda attributes each call to the source application within minutes
- Dashboard shows live cost-per-app, cost-per-model breakdown
- MCP Server lets your AI agents answer: Which app spent the most today?
SETUP (after deploying the CloudFormation stack):
The stack creates the log group and IAM role automatically. You just need to enable logging:
- Go to Amazon Bedrock console - Settings - Model invocation logging
- Check Text (and optionally Image/Video)
- Select CloudWatch Logs, enter log group: /aws/bedrock/invocation-logs
- For IAM role, use the InvocationLoggingRoleArn from the stack outputs
- Save. Done - calls will appear in your dashboard within minutes.
Without this step, the product still works via CloudTrail (5-15 min delay) but enabling invocation logging gives you near-real-time data with full token counts.
Built on CloudTrail and Bedrock Invocation Logging data. Dual-source architecture with automatic deduplication ensures no calls are missed and none are double-counted.
Runs entirely in your AWS account. No data leaves your VPC. Works with all Bedrock models including Nova, Nova 2, Claude, Llama, and Mistral.
IMPORTANT LIMITATIONS: Cost estimates are based on published on-demand pricing and may not reflect reserved capacity or negotiated rates. Calls made through the Bedrock Responses API (bedrock-mantle endpoint) are not captured by AWS invocation logging and will not appear in this product. This product provides estimates for planning purposes only - refer to AWS Cost Explorer for authoritative billing data. Waltsoft is not liable for billing discrepancies or financial decisions made based on data shown.
Pricing: Starter at 29/mo for dashboard and daily digest. Pro at 99/mo adds MCP Server and real-time alerts.
Highlights
Highlighted by the publisher on AWS Marketplace.
Near-real-time cost attribution - minutes not 48 hours
MCP Server lets AI agents query your Bedrock spend
5-minute deploy vs hours of CUR and Athena setup
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Plans and pricing as listed
2 listed- Units
- Units
Refund terms
As stated by the publisher on AWS Marketplace.
14-day free trial available via private offer. Contact support@waltsoft.net for billing questions.
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.