Skip to content

Bedrock Marketplace agreement for Claude Sonnet 4.6 created then instantly expires — INVALID_PAYMENT_INSTRUMENT despite valid payment method

0

I'm trying to invoke Claude Sonnet 4.6 on Amazon Bedrock via the cross-region inference profile us.anthropic.claude-sonnet-4-6, using bedrock-runtime invoke-model. Every attempt fails with:

AccessDeniedException: Model access is denied due to INVALID_PAYMENT_INSTRUMENT: A valid payment instrument must be provided.. Your AWS Marketplace subscription for this model cannot be completed at this time.

Marketplace notification emails confirm each invocation attempt creates a new Marketplace agreement which expires at the exact same timestamp it starts (Agreement start date = Agreement end date) — the subscription is created and instantly voided, every time. Reproduced 9+ times.

Product: Claude Sonnet 4.6 (Amazon Bedrock Edition) Seller: Anthropic, PBC Product ID: prod-ffvjxvh4ltq64 Offer ID: offer-ldnd26nhxx676

Already ruled out payment method as the cause — tested 3 different valid, verified payment methods (2 credit cards + UPI AutoPay), all producing identical failures. Account is on AWS India (AISPL) billing with currency correctly set to INR.

AWS Support (Basic plan) confirmed via their investigation that payment method is not the root cause and that this looks like an agreement entitlement provisioning bug on the Marketplace/Bedrock side, but the case has not been escalated to an engineer. Has anyone else hit this, or does anyone from the AWS Marketplace/Bedrock team have insight?

1 Answer
0

The "INVALID_PAYMENT_INSTRUMENT" error you're encountering when trying to invoke Claude Sonnet 4.6 through Amazon Bedrock indicates that the automatic AWS Marketplace subscription process is failing during the first invocation attempt. When you invoke a third-party model in Amazon Bedrock for the first time, the service automatically initiates an AWS Marketplace subscription. If this subscription cannot be completed, subsequent invocations will continue to fail with access denied errors.

Based on the behavior you're describing—where Marketplace agreements are being created but immediately expiring—this suggests an issue with the subscription provisioning process itself rather than a typical IAM permissions problem. The fact that you've verified multiple valid payment methods and that AWS Support has confirmed the payment method isn't the root cause points to a more complex provisioning issue.

For this type of situation where the automatic subscription mechanism appears to be malfunctioning, I'd recommend adding detailed correspondence to your existing case through the AWS Support Center (https://console.aws.amazon.com/support/). Include the specific timestamps of the failed subscription attempts, the agreement IDs from your Marketplace notification emails, and emphasize that this is blocking your ability to use the service entirely. You might also consider reviewing your AWS Support plan options, as higher-tier plans provide faster response times and access to more specialized technical resources for complex issues like subscription provisioning failures.

It's worth noting that after a subscription successfully completes, it can take up to 2 minutes before the model becomes accessible, and you may continue to see access denied errors during that brief window. However, the instant expiration pattern you're seeing is clearly abnormal and requires investigation by the AWS Marketplace and Bedrock teams.
Sources
Resolve AWS Marketplace permission errors in Bedrock | AWS re:Post

answered 2 months ago

EXPERT

reviewed 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.