Same governance model. Workspace-level allocation.
Claude Platform on AWS bills in CCU via workspace. FinOps Center applies the same Business Request → FinOps Lead approval → Cloud Engineer execution flow to Claude Platform workloads — with workspace as the allocation scope.
The Same Model, Applied
FinOps Center generates what needs to exist.
Cloud Engineer creates it. Product Owner claims it.
The governance workflow is identical across Bedrock and Claude Platform. What FinOps Center generates is different — because the underlying attribution mechanism is different. That's the only thing that changes.
- FinOps Center generates IAM policy + CLI command
- Cloud Engineer applies aws iam put-role-policy
- Product Owner claims IAM role ARN in Spaces
- Attribution flows via CUR 2.0 line_item_iam_principal
- Workload-level attribution per IAM role
- FinOps Center generates workspace name + 3-task CE chain
- Cloud Engineer creates workspace via task queue
- Product Owner claims workspace in Spaces
- Attribution flows via CUR workspace tags
- Workspace-level attribution (portfolio / product scope)
What FinOps Center Handles For You
Claude Platform has a different billing model and scope primitive.
FinOps Center abstracts all of it.
CCU Billing
Claude Platform bills in Claude Consumption Units at $0.01/CCU via AWS Marketplace — not per-token like Bedrock. FinOps Center maps CCU spend to workloads via workspace tags in CUR. Product Owners see CCU consumption against their workspace estimate.
Workspace Scoping
The scope primitive is a workspace, not an account. FinOps Center adds workspace as a fifth dimension to the approval scope — the FinOps Lead names it at approval time, so there is no naming convention ambiguity for the Cloud Engineer when executing the task.
V1 Allocation Scope
In V1, Claude Platform attribution is workspace-level — a workspace maps to a portfolio or product team via CUR tags. This is equivalent to the portfolio-level allocation model. Workload-level attribution (per-application IAM principal) is on the roadmap.
The Cloud Engineer Task Chain
Three sequential tasks. FinOps Center generates them.
Cloud Engineer works through them in order.
When a FinOps Lead approves a Claude Platform model, FinOps Center generates three sequential Cloud Engineer tasks. Each task is blocked until the previous is marked complete.
Cloud Engineer creates the Claude Platform workspace using the exact name the FinOps Lead specified at approval time. The workspace name is passed directly from the approval — no naming decisions required.
Workspace name comes from FinOps Lead approval
Confirm the workspace was created successfully and register the workspace ARN in FinOps Center. Task 3 is blocked until the workspace ID is confirmed in this step.
Workspace ARN registered before proceeding
Task complete. Audit record created with timestamp and Cloud Engineer identity. Product Owner receives notification to claim the workspace in Spaces — enabling CUR tag attribution to their workload.
Product Owner claims workspace in Spaces
Task 2 is blocked until Task 1 is marked complete. Task 3 is blocked until the workspace ARN is confirmed in Task 2. FinOps Center enforces this sequencing — the Cloud Engineer cannot skip steps.
The Approval Scope Model
Five dimensions instead of four — workspace added to the scope.
Bedrock approval scope is model × account × region × IAM scope. Claude Platform adds workspace — because workspace is the allocation boundary. The FinOps Lead names the workspace at approval time and it goes directly to the Cloud Engineer in Task 1.
How It Looks in FinOps Center
One AI Models table. Bedrock and Claude Platform side by side.
Claude Platform rows appear alongside Bedrock rows — distinguished by a teal platform badge. Scope coverage shows workspace count instead of account count. The governance experience in the table is identical.
| Vendor | Platform | Model | Scope Coverage | Status |
|---|---|---|---|---|
| Amazon | Bedrock | Nova Lite | 1 of 5 accounts · 2 scopes | 1 Implemented · 1 Pending task |
| Anthropic | Bedrock | Claude 3 Haiku | 2 of 5 accounts · 4 scopes | 3 Approved · 1 Pending task |
| Anthropic | Claude Platform | Claude Sonnet 4.6 | 1 workspace · 1 scope | 1 Implemented |
| Anthropic | Claude Platform | Claude Haiku 4.5 | 1 workspace · 1 scope | 0 Approved · 0 Pending tasks |
Bedrock rows show “N of 5 accounts”. Claude Platform rows show “N workspace” — the scoping primitive differs, but the governance experience in the table is identical.
Ready to govern Claude Platform spend alongside Bedrock?
FinOps Center deploys via AWS Marketplace and supports Claude Platform from day one — same governance model, workspace-level allocation.