Claude AWS Marketplace: pay Claude from your cloud commit

TL;DR

You can pay for Claude from an existing cloud commitment on all three hyperscalers. On AWS Marketplace, Bedrock tokens, Claude Platform on AWS and Claude Enterprise seats all retire AWS commitments. Microsoft states Foundry usage decrements MACC. For EU data residency with commit drawdown, only Bedrock’s eu. profiles and Google’s eu multi-region qualify today.

Which routes let you pay for Claude through a cloud commitment?

Five routes put Claude on a hyperscaler invoice: three on AWS, one on Google Cloud, one on Microsoft Azure. All of them run through the cloud’s marketplace, so Anthropic remains the seller even when AWS, Google or Microsoft sends the bill. What differs is what you buy (tokens or seats), who processes your prompts, and whether an EU-only processing option exists.

Route	What you buy	Invoice	Commit drawdown	EU processing option	Contract and DPA
Claude on Amazon Bedrock	Tokens, per model	AWS bill, Marketplace line under the model provider	Yes (Anthropic lists AWS commitment retirement)	Yes: eu.anthropic.* geo profiles	Anthropic on Bedrock terms, Anthropic Ireland for EEA customers, Anthropic DPA; AWS operates inference
Claude Platform on AWS	Tokens via CCU at $0.01	AWS bill, one CCU line	Yes (listing: “spend retires against existing AWS commitments”)	No: only us and global	Anthropic Commercial Terms; Anthropic is the processor
Claude Enterprise via AWS Marketplace	Seats plus usage	AWS bill	Yes (listing: draws down EDP or PPA)	Not stated on the listing	Anthropic, claude.ai product
Claude on Google Cloud	Tokens, per model	Google Cloud bill via Marketplace	Yes (Google: draw down spend commitments)	Yes: eu multi-region	Data handling governed by Google Cloud
Claude in Microsoft Foundry	Tokens via CCU at $0.01	Azure invoice, billed by Microsoft	Yes: CCU meter is MACC-eligible	No: Global Standard or US Data Zone only	Anthropic data use terms; Anthropic is an independent processor for Microsoft

The commit column needs one caveat. Each cloud decides eligibility per contract, and none of the public pages promises 100 percent drawdown for your specific agreement. The AWS Marketplace buyer FAQ says products deployed on AWS “typically qualify” and that eligibility is determined per product. Ask your account team for the written answer before you plan a renewal around it.

Google’s statement is older than the others. The Claude 3.7 Sonnet announcement from February 2025 says you can procure Claude on Google Cloud Marketplace and “draw down on your Google Cloud spend commitments”. The 2026 announcements repeat the Marketplace route but not the commit wording. Google also lists “Google Cloud Marketplace offerings” under its discount exclusions, so your negotiated Google Cloud discount does not apply to Claude tokens.

Microsoft is the most explicit. The CCU billing page says CCU spend decrements MACC “the same way any other Azure Marketplace consumption does”, and that CCU billed by other cloud providers does not. The catch for EU teams sits in the deployment types. Claude in Microsoft Foundry offers Global Standard and US Data Zone Standard. There is no EU Data Zone for Claude.

How does Claude on AWS Marketplace show up on your bill?

Claude on Bedrock is a third-party Marketplace product, not a native Bedrock line. The Opus 5.5 model card says charges appear on your AWS bill and in Cost Explorer “under the model provider (not under Amazon Bedrock)”. FinOps dashboards filtered on the Bedrock service miss Claude entirely. Filter on the Anthropic product instead.

The third-party model terms state who you contract with: “Anthropic Services on Amazon Bedrock are sold by Anthropic.” For customers in the EEA, Switzerland or the UK, “Anthropic” means Anthropic Ireland, Limited. The terms (version August 18, 2025) incorporate the Anthropic Data Processing Addendum. Anthropic’s own documentation adds that on Bedrock AWS operates the inference stack and is the inference data processor. Your DPO should read both documents, not only the AWS customer agreement.

Each Claude model has its own Marketplace product ID. Opus 5.5 is prod-e5xo6z26ie45g, launched on Bedrock on September 22, 2026. The model access page explains the mechanics. The first invocation starts the Marketplace subscription in the background, which takes up to 15 minutes. The calling role needs aws-marketplace:Subscribe. Anthropic additionally requires a first-time-use form, once per account or once at the organization’s management account.

If procurement must approve each model before anyone can use it, scope the subscription right to a product ID:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["aws-marketplace:Subscribe", "aws-marketplace:ViewSubscriptions"],
      "Resource": "*",
      "Condition": {
        "ForAnyValue:StringEquals": { "aws-marketplace:ProductId": ["prod-e5xo6z26ie45g"] }
      }
    }
  ]
}

AWS warns that denying aws-marketplace:Subscribe alone does not block the first call, because Bedrock starts the subscription itself. To block a model from the start, deny bedrock:InvokeModel in a service control policy. To check whether your private offer is visible in an account before production traffic starts:

import boto3

bedrock = boto3.client("bedrock", region_name="eu-central-1")
offers = bedrock.list_foundation_model_agreement_offers(
    modelId="anthropic.claude-opus-5-5", offerType="ALL"
)
for o in offers["offers"]:
    print(o)

offerType="ALL" returns public and private offers. If only the public offer comes back, the private offer was extended to a different account ID.

Claude Platform on AWS is a different product. Anthropic operates it, AWS only provides IAM and billing. It bills in Claude Consumption Units at $0.01 per CCU (100 CCU equal one dollar), metered hourly and invoiced monthly in arrears. The Marketplace listing says spend retires against AWS commitments. For EU teams the Claude Platform on AWS documentation is the deciding read: inference geographies are us (1.1x price) and global, nothing else. Workspace storage is US only. Picking eu-central-1 for the workspace changes the gateway endpoint, not where the model runs.

Claude Enterprise seats are a third AWS listing. The public offer is a 12-month contract for 20 seats at $4,800, with usage billed on top at Anthropic API rates and extra seats prorated daily. The listing states that spend draws down your EDP or PPA. If you do not renew before the end date, entitlements expire.

Which procurement steps get Claude onto your cloud invoice?

The order matters more than the paperwork. Private offers are tied to account IDs, discounts start at acceptance and never apply backwards, and Bedrock discounts do not move to Claude Platform on AWS. The sequence below avoids two expensive mistakes: paying list price for weeks, or accepting the offer in the wrong account.

1. Decide the product first. Tokens for applications (Bedrock, Google Cloud, Foundry) or seats for employees (Claude Enterprise). These are separate contracts with separate organizations. Claude Platform on AWS sign-up creates a new Anthropic organization, separate from a Claude Enterprise org bought through AWS Marketplace.
2. Confirm commit eligibility in writing. Ask the AWS, Google or Microsoft account team whether Claude spend retires your specific commitment and at what rate.
3. Pick the accepting account. On AWS, accept from the management or designated billing account. A private offer can name up to 25 accounts, and member accounts that already subscribed must accept the new offer too.
4. Negotiate before the first token. Anthropic’s pricing page states discounts cannot be applied retroactively to usage before the private offer is accepted.
5. Accept, then verify. On AWS, check the license in AWS License Manager in us-east-1, where it is always created. On Azure, confirm the “Claude Platform on Foundry” offer on the billing account.
6. Tag and allocate. Claude shows up as one Marketplace line (or one CCU line). Per-model detail lives in the Claude Console, the Foundry Monitor tab or Bedrock usage logs, so build the allocation before month one closes.
7. Diary the end date. When an AWS private offer expires, you either fall back to public pricing or lose the subscription, depending on product type. Accepting a renewal offer cancels the remaining scheduled payments of the old one.

Three pitfalls cost real money:

• Seats and tokens are billed separately. A Claude Enterprise contract does not cover Bedrock tokens, and a Bedrock private offer does not discount Enterprise seats.
• Old Foundry deployments keep old billing. Microsoft says deployments created before CCU became generally available stay on per-model billing. Moving to CCU needs a new deployment.
• Spend limits lag. On Claude Platform on AWS, spend can take about 2 hours to show, and Anthropic bills the overshoot.

Which cloud should carry Claude for long-term operation?

Test residency first, commitment second. Pick the cloud where your EU processing requirement can be met, then prefer the one holding your largest commitment. If prompts contain personal data that must stay in the EU, only Bedrock with an eu. profile and Google Cloud with the eu multi-region pass today. Foundry and Claude Platform on AWS do not.

Your situation	Route we would pick	Why	When the other route wins
Large AWS EDP, EU personal data in prompts	Bedrock, eu.anthropic.* profile	Commit drawdown plus EU geo profile	Claude Platform on AWS if you need beta features and US or global processing is acceptable
Large Google Cloud commit, EU data	Google Cloud, eu multi-region	Commit drawdown plus EU multi-region	Bedrock if your Claude workloads already sit in AWS accounts
Large MACC, EU data must stay in the EU	Foundry is not enough on its own	No EU deployment type for Claude	Foundry for workloads where global processing is legally cleared
Employees need chat, coding and Cowork seats	Claude Enterprise via AWS Marketplace	Seats on the AWS bill, EDP drawdown	Direct contract with Anthropic if you have no AWS commitment
Several commitments, none dominant	One primary cloud, one fallback	Fewer private offers to renew	Two clouds if availability matters more than procurement effort

Both EU-capable routes cost more than global routing. Anthropic’s pricing page states that Bedrock regional endpoints and Google’s regional and multi-region endpoints carry a 10 percent premium over global endpoints, for Sonnet 4.5 and later. At Opus 5.5 list prices of $4 per million input tokens and $20 per million output tokens, that premium is the cost of residency, and it also burns commit 10 percent faster.

The legal comparison of the providers, including ZDR and processor roles, is in our Claude GDPR provider comparison. Token prices per cloud are in the Claude API pricing guide for the EU. How Bedrock’s regions and geo profiles work in detail is in the Amazon Bedrock EU guide.

Run it yourself or outsource?

Paying through a cloud commit is mostly procurement and FinOps work, not engineering. In-house, it needs a named owner for each private offer, a FinOps analyst who reconciles Marketplace or CCU lines with per-model usage every month, and a cloud admin who controls who may subscribe. For one cloud and one product, we would keep it in-house.

The recurring tasks are predictable. Someone tracks offer end dates and renewal terms. Someone checks whether new models (each with its own Bedrock product ID) were subscribed in the right account. Someone allocates a single CCU line back to teams. Someone re-reads the DPA when Anthropic or the cloud updates terms; the Bedrock terms we read are dated August 18, 2025. Our estimate, not a sourced figure: a few hours per month for one cloud, more around renewals.

Outsourcing to a managed service provider makes sense when you buy Claude on two or more clouds, when nobody in the company owns FinOps, or when renewals have already lapsed once. It makes little sense if a single AWS account and one Bedrock offer cover everything.

What to demand from a provider for this topic:

• SLA on renewal handling and on monthly cost reports, with a fixed date.
• AVV/DPA with the provider itself, plus its subprocessor list, if it can see your billing data or usage logs.
• Access model: read-only billing access by default. The provider should not hold aws-marketplace:Subscribe or the right to accept private offers in your name.
• Exit: private offers, Marketplace subscriptions and commitments stay in your accounts. Nothing should be bought through the provider’s own account if you want to leave without re-papering.

FAQ

Does Claude on Bedrock count toward my AWS EDP?

Anthropic lists AWS commitment retirement as a property of Bedrock and Claude Platform on AWS. AWS says Marketplace products deployed on AWS typically qualify, with eligibility per product. Get the rate for your own agreement in writing.

What does Claude Enterprise cost on AWS Marketplace?

The public offer is $4,800 for 20 seats over 12 months, with usage on top at Anthropic API rates and extra seats prorated daily. Private offers can differ. The listing says spend draws down EDP or PPA.

Claude Platform on AWS vs Bedrock: which one for EU data?

Bedrock. Its eu.anthropic.* profiles keep data within EU regions. Claude Platform on AWS supports only us and global inference, and its workspace storage is US only.

Does Claude in Microsoft Foundry draw down MACC?

Yes. Microsoft states the CCU meter is MACC-eligible and billed on your Azure invoice. CCU billed by other clouds does not decrement MACC. Foundry offers no EU deployment type for Claude.

Can I move a Bedrock private offer to Claude Platform on AWS?

No. Anthropic says negotiated discounts and Marketplace private offers do not transfer automatically between the two. Set up the new offer before the first request, because discounts do not apply retroactively.

What happens when a Marketplace private offer expires?

On AWS you either fall back to public pricing or lose the subscription, depending on product type. For Claude Enterprise, entitlements expire if you do not renew before the end date.

Sources

1. AWS: Serverless third-party model terms (Anthropic) (1 October 2026)
2. AWS: Claude Opus 5.5 model card (1 October 2026)
3. AWS: Request access to Bedrock models (1 October 2026)
4. AWS Marketplace: Private offers (buyer guide) (1 October 2026)
5. AWS Marketplace: Claude Enterprise listing (1 October 2026)
6. AWS Marketplace: Claude Platform listing (1 October 2026)
7. Anthropic: Claude Platform on AWS (1 October 2026)
8. Anthropic: Pricing (1 October 2026)
9. Anthropic: Data residency (1 October 2026)
10. Anthropic: Claude on Google Cloud (1 October 2026)
11. Anthropic: Claude in Microsoft Foundry (1 October 2026)
12. Microsoft Learn: Claude consumption units (CCU) billing in Foundry (1 October 2026)
13. Google Cloud blog: Claude 3.7 Sonnet on Vertex AI (1 October 2026)