Skip to content

INVALID_PAYMENT_INSTRUMENT after requesting model access in Amazon Bedrock

3

Hi,

I was trying to use the GA Amazon Bedrock, but I received the following error when I tried to request models access:

Amazon Bedrock errors

This account has been active a few years and we're currently using many other services without any troubles. They payment methods are properly set in our organization and, again, there have been no issues so far on other services.

Did I miss any configuration somewhere?

Thanks in advance!

asked 3 years ago20.7K views

8 Answers
3
Accepted Answer

I resolved this issue by changing our default payment method from a SEPA type to a CREDIT CARD type. I was able to complete the purchase through Bedrock, and change our defaults back afterwards.

answered 3 years ago

EXPERT

reviewed 2 years ago

EXPERT

reviewed 2 years ago

  • Yes! Definitely that was it and that's how we solved it on our side. I forgot to post the answer here. It took a while before we understood the issue.

    Thanks!

  • I have added credit card but still same error is coming: An error occurred (AccessDeniedException) when calling the Converse operation: 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.

  • You also might need to regenerate API keys after changing the payment method

2

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.

I get this error popup when I try to invoke any model from aws bedrock (using playground). First time when I get error for any specific model, it get active in marketplace subscription, and in second attempt it moves to inactive state with same error.

I tried all the ways,

  1. I setup a credit card in payment method,
  2. I set it up as default payement method also,
  3. I set my region with us-east-1,
  4. Raised the support case also.

But nothing happend. If anyone here can help me with this issue, It would be very helpful.

Thanks!!!!

answered 3 months ago

  • Exactly same problem, Were you able to solve it ?

1

The solution without changing default payment method as pointed out by AWS support was:

  • under Billing and Cost Management -> Preferences and Settings -> Payment Preferences -> Payment methods
  • make sure you have one Credit Card (does not need to be default payment method)
  • under Billing and Cost Management -> Preferences and Settings -> Payment Preferences -> Payment profiles
  • create one payment profile for each listed services provider ending with "- Marketplace" and point it to the Credit Card

Works for our accounts now. We set it up like that in the payer account of our AWS Organization and it works even when activating models in member accounts.

answered a year ago

  • We have SEPA (EUR) as default and a Creditcard (EUR) as backup setup in the root account of our aws-organization. Switching the default payment method was not an option for us.

    To make it work we needed to create multiple "Payment Profiles" for the "Service Providers":

    • "AWS Inc."
    • "AWS Inc. - Marketplace"
    • "AWS EMEA - Marketplace"

    All needed to use the Currency "USD - US Dollar" and Referenced our Creditcard.

1

I cannot find "Payment profiles" section anywhere, why is it?

answered a year ago

0

I have additional info. I cannot subscribe to Foundation Models in Amazon SageMaker either. Inspecting the Network tab in the developer tools of my browser, the requests return the same error for the model subscription no matter which region I'm in.

There's definitely something wrong with my account.

answered 3 years ago

0

Please note, SEPA is not the only type of payment type not supported for Marketplace. Per this blog post, some India based customers will also be affected. As others have already called out, you can update your payment preference in the console.

AWS

answered 2 years ago

EXPERT

reviewed 2 years ago

0

Credit card customers with EMEA SOR also face this issue and can be resolved by getting the payment method on the AWS account temporarily converted to net term with help of AWS Billing team.

AWS
MODERATOR

answered a year ago

0

Does not work for me, no errors.

answered 5 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.