SupportedCloudBring your AWS bill into the same view as everything else
Track AWS spend every day per service and account, with Amazon Bedrock and Claude on Bedrock counted as AI. Split it by team with a cost allocation tag.
Highlights
One connection, every account
Connect the management account and RootSpend sees every member account under it, per service and per day.
AI lands in AI
Bedrock, Claude on Bedrock and SageMaker go to the AI tools category, next to OpenAI and Claude, instead of hiding inside the cloud total.
Teams by tag or account
Give a whole account to a team, or set one cost allocation tag key and let the tag values decide.
What you get from AWS
- Daily cost per service and linked account, credits and refunds included
- Amazon Bedrock and Claude on Bedrock under AI tools
- Spend per team from a cost allocation tag (optional)
- Linked accounts you can hand to a team
- Budgets, forecasts and spike alerts
What it doesn't do yet
- Cost per person. AWS bills have no users, so teams claim accounts or use a tag.
- The last 14 days are AWS estimates. Credits, refunds and tax can still change them, and RootSpend picks up the changes.
- AWS charges its own small Cost Explorer fee, about $0.01 per request, a few per sync.
Your cloud bill, next to your AI bill
AWS is often where your AI and data products actually run. Seeing it next to OpenAI, Claude and Snowflake gives you the real total, not three separate invoices.
How it works
You connect the management account with Cost Explorer read access, ideally through a read only role. Every day, RootSpend reads cost per service and per linked account. Set a cost allocation tag key and the split happens per tag value instead, so a team tag maps straight onto your teams.
AI services like Amazon Bedrock and Claude on Bedrock are recognised and counted as AI tools. That way "what does AI cost us?" includes the models you run on AWS.
AWS questions
Cost Explorer read access, ideally through a read only role. You give an access key for a user that can only assume that role, the role's ARN, and an external ID.
Marketplace lines are flagged, so a category rule can leave them out and the same spend isn't counted twice.
The unblended cost, which is what your invoice shows before savings plans and reserved instances are spread over time.
Want to see your AWS spend split by team?
RootSpend is opening to a first group of teams soon. Join the waitlist, or book a demo and we will show you on sample data.
Opening soon. The waitlist gets in first.