https://kane.mx/tags/cost-allocation/Recent content in Cost Allocation on The roadHugo -- gohugo.ioenWed, 29 Apr 2026 00:00:00 +0000https://kane.mx/posts/2026/claude-code-cost-per-project/Wed, 29 Apr 2026 00:00:00 +0000https://kane.mx/posts/2026/claude-code-cost-per-project/ <p>If you run <code>claude</code> against Amazon Bedrock across a dozen repos, your bill arrives as one opaque number. Until recently, the workaround was clunky — create an application inference profile per project, swap them by hand, hope you remembered which one was active. In April 2026, AWS <a href="https://aws.amazon.com/blogs/machine-learning/introducing-granular-cost-attribution-for-amazon-bedrock/">shipped native per-principal cost attribution for Bedrock</a>: every <code>InvokeModel</code> call now carries the caller's IAM principal and session tags straight into Cost Explorer and CUR 2.0. That is enough to turn a ~60-line shell recipe into a per-repo billing system.</p> <p><a href="https://kane.mx/posts/2026/claude-code-cost-per-project/">Read More</a></p>