I use Claude Code on EC2 through Amazon Bedrock. When I tried switching the model from Claude Opus 4.8 to Claude Opus 5.5, it failed with a 403 error. Claude Code was up to date, the IAM role was allowed to call Bedrock, and Claude Opus 4.8 worked fine. Only 5.5 refused.
Short answer: it was neither a misconfigured IAM role nor an app bug. Bedrock needs a one-time step the first time a model is used in your account. After calling Claude Opus 5.5 once from an admin role with AWS Marketplace permissions, the EC2 IAM role could use it normally too.
Symptom
Switching to Claude Opus 5.5 with /model in Claude Code gives this error (jp. is the Japan cross-region inference profile; yours may be us., global. etc.):
❯ /model jp.anthropic.claude-opus-5-5 ⎿ API error: 403 Model access is denied due to IAM user or service role is not authorized to perform the required AWS Marketplace actions (aws-marketplace:ViewSubscriptions, aws-marketplace:Subscribe) to enable access to this model. Refer to the Amazon Bedrock documentation for further details. Your AWS Marketplace subscription for this model cannot be completed at this time. If you recently fixed this issue, try again after 2 minutes · model not changed
Switching back to Claude Opus 4.8 works without a hitch:
❯ /model jp.anthropic.claude-opus-4-8 ⎿ Set model to Opus 4.8 and saved as your default for new sessions
The error says aws-marketplace:Subscribe is needed. But 4.8 worked, so at first I assumed “the Anthropic subscription should be shared; one model should unlock them all.” That was the wrong assumption.
Cause: the subscription is per model
The Amazon Bedrock documentation explains how it works:
- Third-party models such as Anthropic’s are offered through AWS Marketplace, with a subscription required for each model
- The subscription is created automatically the first time the model is invoked in your account
- To create it automatically, whoever makes that first call (IAM user, role) needs Marketplace permissions such as
aws-marketplace:Subscribe. Without them you getAccessDeniedException - Once anyone has enabled it, other users, roles in the account can invoke it without Marketplace permissions
That explains everything. Claude Opus 4.8 worked because someone in this account had used it before, creating the subscription. Claude Opus 5.5 was new, so it had no subscription yet. The first call came from the EC2 IAM role, which lacks Marketplace permissions, so the subscription couldn’t be created, hence the error.
The IAM role had permission to “invoke Bedrock”, but not to “enable a new model for the first time”. The key point is that these are two different things.
The “Model access” page is gone
Search online and you’ll often find instructions to “request the model on the Bedrock console’s Model access page”. Claude Code suggested the same. But opening that page in the console shows a notice that it has been retired.
The notice says, in short: serverless models are now enabled automatically the first time they’re invoked in an account, so manual enabling is no longer needed. Models offered through AWS Marketplace, however, must be invoked once by a user with Marketplace permissions, after which every user in the account can use them. Don’t get lost looking for the Model access page from an outdated guide.
Fix: invoke it once from a role with permissions
The fix is to invoke the model once as a user or role with Marketplace permissions. No API code needed: pick the model in the Bedrock console playground, send a word. I switched to a role with admin rights, then sent “hello” to Claude Opus 5.5 in the playground.
Here I got stuck once more: even from the admin role, I first got the same error.
AccessDeniedException Model access is denied due to IAM user or service role is not authorized to perform the required AWS Marketplace actions (aws-marketplace:ViewSubscriptions, aws-marketplace:Subscribe) to enable access to this model. Refer to the Amazon Bedrock documentation for further details. Your AWS Marketplace subscription for this model cannot be completed at this time. If you recently fixed this issue, try again after 2 minutes.
If even an admin was denied, I suspected an organization policy (SCP) blocking Marketplace actions. But after waiting a bit, reloading the page, then sending again, I got a normal reply.
The official docs also say the subscription takes time to complete, with errors possible meanwhile. The “try again after 2 minutes” at the end of the error message meant exactly that. If a role with permissions gets an error once, don’t blame organization policy right away; wait a few minutes, then retry.
Once it went through in the playground, the EC2 IAM role could switch too. I added no permissions to the EC2 role.
❯ /model jp.anthropic.claude-opus-5-5 ⎿ Set model to Opus 5.5 and saved as your default for new sessions
I don’t recommend adding Marketplace permissions to the EC2 role
Adding aws-marketplace:Subscribe etc. to the EC2 IAM role would let it create subscriptions directly. But that permission lets it subscribe to new Marketplace products, which I don’t think belongs permanently on EC2 for everyday use. Having an admin with permissions invoke a new model once, when you start using it, is safer.
Notes
Anthropic models also need a one-time use case form
The first time an account uses Anthropic models, you also have to submit a form describing your use case. This is once per account, not per model (with AWS Organizations, once in the management account). Claude Opus 4.8 already worked for me, so that was done. If you’re using Claude on Bedrock for the first time, you’ll need it as well.
A model set by environment variable comes back in new sessions
When I switched to 5.5 in Claude Code, this also appeared:
ANTHROPIC_MODEL is set to Opus 4.8 — new sessions use that while it is set
If you set the model with the ANTHROPIC_MODEL environment variable, it takes precedence. Even after switching with /model, the next new session goes back to the environment variable’s model, so update the variable too if you want to keep using the new one.
How it differs from “is not available for this account”
When trying a new Claude model on Bedrock, you may also see this very similar error:
AccessDeniedException anthropic.claude-opus-5-5 is not available for this account. You can explore other available models on Amazon Bedrock. For additional access options, contact AWS sales at https://aws.amazon.com/contact-us/sales-support/
The model ID at the start (anthropic.claude-opus-5-5 here) changes with the model you tried, e.g. anthropic.claude-opus-4-8. Whatever the ID, the way to tell them apart, plus the order to check things, is the same.
It’s the same AccessDeniedException (403), but most likely a different cause from this post’s. Tell them apart by whether the message names AWS Marketplace actions (aws-marketplace:ViewSubscriptions, aws-marketplace:Subscribe).
| Error message | Likely cause | Fix |
|---|---|---|
| not authorized to perform the required AWS Marketplace actions (aws-marketplace:ViewSubscriptions, aws-marketplace:Subscribe) | No permission to create the Marketplace subscription on first invocation (this post) | Invoke it once from a role with Marketplace permissions |
| is not available for this account | One of the causes below | See the checklist below |
I couldn’t find AWS documentation explaining “is not available for this account” word for word. Below are possible causes I gathered from the official docs plus reports on AWS re:Post. I haven’t hit this error myself, so this is a summary of research only.
Similar symptoms in the official docs
- The Marketplace subscription is still processing: right after the first invocation, calls can be refused while it processes. Wait about 15 minutes, then retry
- The Marketplace agreement failed: an invalid payment method, regional restrictions etc. are given as causes. Check the error message, fix the cause
- An organization SCP denies it: check whether an AWS Organizations service control policy blocks Bedrock invocations
Per the official docs, if the Anthropic use case form hasn’t been submitted, you get a different error, FTUFormNotFilled (404).
Reported on AWS re:Post
- The new model isn’t available to that account yet: often reported for just-released models such as Claude Opus 5, Claude Sonnet 5, Claude Opus 4.8.
aws bedrock get-foundation-model-availabilityshows “AUTHORIZED”, “AVAILABLE”, yet invocations are refused. Some report the management account of an Organization can invoke it while member accounts can’t. Answers suggest new models are opened up gradually (based on usage history, for example), recommending AWS Support if waiting doesn’t help - No model agreement in place: some report it was fixed by checking offers with
aws bedrock list-foundation-model-agreement-offers, then creating one withaws bedrock create-foundation-model-agreement - Wrong model ID or region: check you aren’t using a model ID unavailable in that region, or an inference profile that isn’t enabled
Order to check
- If the message names AWS Marketplace actions, try this post’s fix (invoke once from a role with permissions)
- Check the model’s status with
aws bedrock get-foundation-model-availability --model-id <model ID> - Check the model ID, region, inference profile are correct
- Check whether an AWS Organizations SCP blocks it
- If it still fails, contact AWS Support with the error message, region, model ID, the
get-foundation-model-availabilityoutput
Summary
- If older models work on Bedrock but only a new one returns 403, ask “is this the first time this account uses this model?” before digging into IAM policies
- Third-party models get their AWS Marketplace subscription per model, not shared across Anthropic, created on first invocation. That requires Marketplace permissions
- The “Model access” page is retired. Once an admin with permissions invokes the model (e.g. in the playground), anyone in the account can use it
- Even a role with permissions can get an error at first. Wait a few minutes, retry
- This repeats with every new model, so remember it when switching models to save time
- The similar “is not available for this account” most likely has another cause. Check whether the message names AWS Marketplace actions
References
- Access Amazon Bedrock foundation models - Amazon Bedrock
- Resolve Amazon Bedrock serverless foundation model access denied errors | AWS re:Post
- Troubleshooting Amazon Bedrock API Error Codes - Amazon Bedrock
- Bedrock: get-foundation-model-availability reports AUTHORIZED/AVAILABLE but InvokeModel returns AccessDenied “not available for this account” | AWS re:Post
- Bedrock: Access denied for latest Claude models like Sonnet 5 and Opus 4.8, while older ones works | AWS re:Post


コメント