Claude Platform on AWS vs Bedrock: A FinOps Reality Check | CloudYali<br>Skip to main content<br>Back to Blog

Claude Platform on AWS gives AWS-heavy enterprises a single AWS Marketplace invoice for Anthropic Claude usage, billed in Claude Consumption Units (CCUs). Per-token cost is identical to Bedrock and the direct Anthropic API. None of the three paths apply EDP service-discount rates to Anthropic model fees. The real FinOps trade-offs are commitment retirement, cost attribution loss, and cross-account workspace constraints.<br>TL;DR<br>Per-token cost is the same across Bedrock, Claude Platform on AWS, and the direct Anthropic API. EDP discount rates don't apply to third-party model fees on any path.<br>EDP retirement is the open question. Anthropic's blog claims "fully retires against existing commitments." AWS's own pages don't repeat that claim. Get the percentage in your private offer in writing before you sign.<br>Bedrock has better native cost attribution. Per-model, per-token-type line items in CUR + Application Inference Profiles + IAM-principal allocation. Claude Platform on AWS collapses to a single CCU line on your AWS bill.<br>One workspace per AWS region per account. Clean per-team chargeback through workspace isolation requires multi-account topology.<br>The bigger shift: AI vendor consoles are now primary FinOps data sources, not secondary references. Plan reconciliation work into your monthly close.<br>Anthropic and AWS shipped Claude Platform on AWS last week and the procurement and security teams across every AWS heavy enterprises would be secretly celebrating this announcement, and in a way it is obvious. One bill, IAM credentials you already have, CloudTrail visibility you already trust, no parallel vendor contract to manage. If you've ever had to onboard Anthropic as a separate vendor through your legal and security review processes, you already know why procurement is so thrilled about this. But I've been reading the launch materials with the FinOps brain switched on, and there's a bunch of stuff in there that's either getting under-reported or actively misread by most people writing about it, so let me walk through what I'm seeing.<br>The three-layer split nobody's naming clearly<br>Forget the word "platform" for a second because it's not really helping anyone read this product correctly. Here's what's actually going on inside any cloud-AI offering. Every one of these things has three layers going on, where your data gets processed, where your IAM and access controls live, and where the money settles. Bedrock owns all three of these layers cleanly. Your prompt stays inside the AWS security boundary, your IAM policies decide who hits what model, the bill comes out of AWS. The direct Claude API owns all three differently but just as cleanly. Your data goes to Anthropic, Anthropic issues the API keys, Anthropic sends you the invoice every month. Whichever way you go, the three layers all sit in one place and you know exactly what you're dealing with.<br>What Anthropic and AWS just shipped does this weird split that nobody else has done quite like this. Anthropic keeps the data plane and spells this out plainly in their launch blog, your inference happens outside the AWS security boundary, and the Anthropic docs for the product even mention that inference "may route to Anthropic's primary cloud" and "subservices may move under the hood without notice," which is the kind of language you write when you really want people to understand that AWS is not the data processor here. AWS gets the IAM and CloudTrail piece, which actually consolidates the auth and audit story for AWS-heavy enterprises in a way that matters at procurement and security. And then the billing runs through AWS Marketplace as this virtual currency called Claude Consumption Units, where 100 CCUs equals one dollar of Anthropic spend after whatever discount you negotiated in your private offer. The procurement story is built entirely on the IAM piece and the billing piece, and the procurement teams getting excited about those pieces are reading the launch blog correctly. But the data plane piece is where all the FinOps consequences are hiding, and that's the part I don't see anyone reading carefully enough.

Three paths to Claude, three different ways the data, control, and commercial layers get splitWhat changes when the bill arrives<br>The FinOps regression here has more teeth than the early writeups have noticed. On Bedrock today, every single Claude call produces four separate line items in your Cost and Usage Report, input tokens, output tokens, cache reads, cache writes, and the usage type field tells you exactly which model, which region, which service tier, which routing pattern. You can wrap any model in an Application Inference Profile, slap your own cost allocation tags on that profile, and the tags flow into Cost Explorer and CUR 2.0 like any other AWS service. As of April this year you can allocate spend by IAM principal directly, which makes...