Cost reporting and budgets
The Billing section reports what a tenant’s connected AWS accounts are spending, read from the customer’s own AWS Cost Explorer. It exists so the person who deployed infrastructure can also answer “what does it cost”, per client, without opening the AWS console.
Two boundaries define it honestly:
- Access is opt-in per connection. Billing works only when the
connection was created with billing data included, which adds a
separate read-only Cost Explorer policy to the discovery role. Without
it, no
ce:*access exists and the report stays empty. - StackTakt detects nothing and enforces nothing here. Figures are unblended cost from Cost Explorer; anomalies are mirrored from AWS Cost Anomaly Detection monitors you configure in AWS.
Syncing
Section titled “Syncing”Spend data updates when an operator selects Sync billing data; there is no schedule. A sync reads each account on its own, so one unreadable account fails by name while the others land, and the report says how old each account’s data is. Page loads never call AWS: everything renders from the last synced snapshot.
The report
Section titled “The report”- Month to date, projection, run rate, prior month, with a pace comparison against the same days last month.
- Where the money goes: by service, by region, by AWS account, and by individual asset where AWS serves resource-level data (a trailing 14-day window).
- Attribution splits spend four ways that add up: deployed by StackTakt, in inventory but deployed elsewhere, not in inventory, and no resource on the bill (tax, support, data transfer). Nothing is absorbed into “other”.
- Biggest movers: what changed this week, not this month.
- Anomalies: findings from your AWS anomaly monitors, shown beside the spend they explain.
Organization scope shows every tenant side by side. Tenants reporting in different currencies are never summed into a fake total; each figure stands on its own.
Budgets
Section titled “Budgets”A budget is the tenant’s monthly target, set by an operator. It drives the pace reading (On track, At risk, Over budget) and the projection against the threshold you chose. It is a StackTakt number: it does not create an AWS Budget, and nothing is stopped or alerted when spend passes it. If you need enforcement, set an AWS Budget in the account as well.