[BUG] Bedrock: Claude Opus 4.7 returns permission_error despite AUTHORIZED entitlement status

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/49238

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Why this is not a duplicate of #49238:

Issue #49238 was a 400 invalid_request_error: "invalid beta flag" — a client-side request formatting problem (Claude Code was sending a beta header that Bedrock didn't recognize). That was resolved by fixing the client.

Our issue is a permission_error: "anthropic.claude-opus-4-7 is not available for this account" — an account-level entitlement/authorization problem on Anthropic's runtime side. The request format is valid (same request works for Opus 4.6). The issue is that:

get-foundation-model-availability returns AUTHORIZED + AVAILABLE
list-inference-profiles shows the model as ACTIVE
Yet the runtime rejects with a permission error

Addendum: Quotas and Entitlements Confirmed

All AWS-side checks pass — the block is on Anthropic's runtime layer.

Service Quotas (non-zero, healthy)

aws service-quotas list-service-quotas --service-code bedrock --region us-east-1 \
  --query "Quotas[?contains(QuotaName, 'Opus') && contains(QuotaName, '4.7')]"

Quota                                                                                                                              Value
Cross-region model inference tokens/min for Anthropic Claude Opus 4.7                   15,000,000
Global cross-region model inference tokens/min for Anthropic Claude Opus 4.7        15,000,000

Entitlement Status

aws bedrock get-foundation-model-availability --model-id anthropic.claude-opus-4-7 --region us-east-1

Field                                 Value
agreementAvailability	AVAILABLE
authorizationStatus	        AUTHORIZED
entitlementAvailability	AVAILABLE
regionAvailability	        AVAILABLE

Inference Profiles

aws bedrock list-inference-profiles --region us-east-1 \
  --query "inferenceProfileSummaries[?contains(inferenceProfileId, 'opus-4-7')].{id:inferenceProfileId, status:status}"

Profile ID                                          Status
us.anthropic.claude-opus-4-7         ACTIVE
global.anthropic.claude-opus-4-7  ACTIVE

Summary

Every AWS control plane check confirms this account is authorized and provisioned for Opus 4.7. The permission_error is originating from Anthropic's runtime behind Bedrock, not from AWS IAM, entitlements, or quotas.

Commenting to say I have the same issue. Reached out on aws support chat (sales) as the error states, to no avail. Also have admin access policy, and on us-east-1. 4.6 is working fine as always- this newer model only returns the same error:

ValidationException
The model returned the following errors: {"type":"error","request_id":"req_53moalmez7mmete26kseeghquow2ieie4tovdwyzxm2bkjffcexa","error":{"type":"permission_error","message":"anthropic.claude-opus-4-7 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/"}}

To restate very plainly, as it pertains to the "reach out to sales" message. I have reached out, and our AWS rep isn't clear on what's going on. Per my last comment above, when inspecting via the aws cli, it appears that we have both model availability and a quota — so, technically, I can't see what's wrong. However, when we look at our AWS Dashboard on Bedrock's Quota page, we see Not supported to request a quota increase.

So, I have no idea how to go about realizing a fix here. So, strictly speaking, perhaps this isn't a software bug per se. Perhaps all the systems are working as expected — but this is certainly a policy bug, because I'm chasing my tail for the whole day, and the solution is absolutely opaque to me.

<img width="1612" height="588" alt="Image" src="https://github.com/user-attachments/assets/892bb9b6-9ddd-4336-84bb-99baaa138f02" />

Same issue here on us-east-1. Confirming the AUTHORIZED-but-denied state described in the OP.

Environment

• Region: us-east-1
• Model IDs tested (all fail): us.anthropic.claude-opus-4-7, global.anthropic.claude-opus-4-7
• Last working on same account/credentials: us.anthropic.claude-opus-4-6-v1 (works fine)
• Reproduced in the AWS Bedrock Console Playground, so not an SDK or CLI issue
• IAM: AmazonBedrockFullAccess + AmazonBedrockMarketplaceAccess + AWSMarketplaceFullAccess attached directly, no SCP restrictions

Runtime error

{
  "type": "error",
  "request_id": "req_7mdkrqg3lg7p5pwrfnyrreeqs7wpu2fofcru4u7xlxqwegz4uk4a",
  "error": {
    "type": "permission_error",
    "message": "anthropic.claude-opus-4-7 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/"
  }
}

Control plane disagrees — reports fully authorized

$ aws bedrock get-foundation-model-availability \
    --model-id anthropic.claude-opus-4-7 \
    --region us-east-1
{
    "modelId": "anthropic.claude-opus-4-7",
    "agreementAvailability": { "status": "AVAILABLE" },
    "authorizationStatus": "AUTHORIZED",
    "entitlementAvailability": "AVAILABLE",
    "regionAvailability": "AVAILABLE"
}

Account ID redacted but happy to share privately with an Anthropic/AWS engineer if it helps correlate on the runtime entitlement side.

I have the same issue.

Can confirm same issue. All other model/endpoint worked. Tried different inference profiles, no luck.

Having the same issue as well.

I've heard back from AWS Support, and can confirm that Opus 4.7 is gated in a way that's not visible via the public API. At least for now, it seems like this is a "call your rep" situation. I'll update again once we find a resolution. I'd appreciate it if anyone could do the same.

In the meantime, this doesn't seem to be a technical or configuration issue.

If we request they open it for the account or we only need to wait?

I've heard back from AWS Support, and can confirm that Opus 4.7 is gated in a way that's not visible via the public API. At least for now, it seems like this is a "call your rep" situation. I'll update again once we find a resolution. I'd appreciate it if anyone could do the same. In the meantime, this doesn't seem to be a technical or configuration issue.

It seems to have resolved for me, I am not sure what changed in the background

It seems to have resolved for me, I am not sure what changed in the background

I also get error in the playground UI from models catalog. which region are you working with?

<img width="1554" height="782" alt="Image" src="https://github.com/user-attachments/assets/9877a6cc-362b-4ccf-805f-f96a695126b2" />

us-east-1
tried it on the playground and it worked. then with api using
global.anthropic.claude-opus-4-7

On Wed, Apr 22, 2026 at 3:48 PM Ali Mirzaei @.***>
wrote:

alimirzaei left a comment (anthropics/claude-code#51183) <https://github.com/anthropics/claude-code/issues/51183#issuecomment-4296330962> It seems to have resolved for me, I am not sure what changed in the background I also get error in the playground UI from models catalog. which region are you working with? — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/51183?email_source=notifications&email_token=A2HMGRMNGGZKNO7FMFGHG7T4XC5S3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRZGYZTGMBZGYZKM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4296330962>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2HMGRLL2LV67PYB3HNHKPL4XC5S3AVCNFSM6AAAAACX7YMUCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOJWGMZTAOJWGI> . You are receiving this because you commented.Message ID: @.***>

I also still get the same error; anyone else able to get it fixed?

+1 Also started working for me. AWS Quota still shows - for RPM, 15M TPM.

Bedrock model playground and Claude Code via Bedrock also works. Without reaching out to sales or anything.

These env vars for claude code finally got it to work for me:

CLAUDE_CODE_USE_BEDROCK=1 ANTHROPIC_MODEL="global.anthropic.claude-opus-4-7" CLAUDE_CODE_USE_MANTLE=1 AWS_REGION=us-east-1

Confirming @nickyli98 's message. 4.7 started working for us. Quotas still read as not supported.

Claude Code worked with AWS Bedrock for a few days (Claude Code ~2.1.11x), but now seems from ~2.1.12x, it doesn't work again, with only dreadful "...retry x/8 and no error message like before) ... checked AWS Bedrock Management Console: both geo and global quotas are zero, aws cli confirms too:

aws service-quotas list-service-quotas --service-code bedrock --region us-east-1 \
  --query "Quotas[?contains(QuotaName, 'Opus') && contains(QuotaName, '4.7')]" 

... value: 0.0

despite authorized:

 aws bedrock get-foundation-model-availability \                                   🕒 12:10
    --model-id anthropic.claude-opus-4-7 \
    --region us-east-1
{
    "modelId": "anthropic.claude-opus-4-7",
    "agreementAvailability": {
        "status": "AVAILABLE"
    },
    "authorizationStatus": "AUTHORIZED",
    "entitlementAvailability": "AVAILABLE",
    "regionAvailability": "AVAILABLE"
}

<img width="1407" height="303" alt="Image" src="https://github.com/user-attachments/assets/8c93c8bb-5a43-4e3b-be40-0cb97a32f332" />

Submitted on AWS "quota increase requests", wait and see...

I found the probable cause. The quotas are zero and that is limiting you for using the models. there are three dots as shared by charles-cai so basically click on the three dots and then you have request increase quota TPM and RPM , just click the TPM and write a big number like 100,000,000 and send the request (if it is too big then it will warn you) so then just put the biggest possible number and send it. it will take some time to be reviewed and then it will be activated. I just did it for both Claude 4.7 models and then you have to wait for it. it seems like a slow process 4-5 days. I hope it works please try it out and I hope we get it solved!

I did request quota increase (from zero), and got rejected :( there was a real person responding to my request but he said after talking with service team, because I'm not using 90% of the existing quota hence the rejection, and I could request again next billing month... so still not solved.

Sigh, I tried the new "Claude Platform on AWS" https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws, but got another error - should be raising a new ticket on this one in CC: API Error: 400 Missing 'anthropic-workspace-id' header. (which I did supply via environment variable).

I feel you. I used a lot of the capacity and I am almost out of credits so perhaps I will have chance to get accepted, I am rate limited in all requests by minute and day on all available models. I see it was much easier to use Claude code to keep track of the usage. and even better is the Github copilot from first of June since it will also apply the pay as you go with the credits. AWS was good to test and try but it is causing too much complication and confusion. I used Github Copilot to set it up :))
I hope you also find a solution soon. If you have used Claude Opus 4.7 you know how powerful it is in one run it always fixes all issues for me (but it is very expensive) :(

OK, good news: after some trial and error, based on https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws I replaced my existing ~/.env for AWS Bedrock with Claude Platform on AWS environment variables: created a new account registration via AWS Marketplace -> Claude Console + new API key, back and forth between AWS Claude Platform Console and Claude Console), and it worked, i.e. now my Claude code is powered by Claude Platform on AWS, Opus 4.7 is there as the default.

The billing is still on AWS so all our credits should still work; thought granular console via Claude Workspace is big weird, I can only see / create one workspace, but I still can create more API keys, so at least I have segregation for different projects or by different team members.

Next see how stable / rate limiting it might be, and how the billing / cost splitting works.

I also got some issue in claude Opus 4.7 and Opus 4.6, but it worked with Opus 4.5 and other anthropic model.
Wandering here, how to make it work for me.

<img width="1853" height="810" alt="Image" src="https://github.com/user-attachments/assets/ef08b053-679c-4ec8-a5cc-ced54f986360" />

I had no luck restoring access through an AWS support ticket, so sharing this since someone else might be in the same boat:

I understand that your applied account-level quota for the Anthropic Claude Opus 4.7 model is currently showing as 0, which is preventing inference calls. I can see that you were able to use this model in April 2026. Due to the high demand and advanced capabilities of Claude Opus 4.7, access requirements for this model have been updated. Access to this model requires additional account validation to ensure appropriate usage patterns. Your account currently does not meet the eligibility criteria for this specific model tier at this time. I apologize for any inconvenience this change may cause. In the meantime, I recommend: - Using alternative Claude models such as Claude 3.5 Sonnet or Claude 3 Opus, which offer excellent performance for most use cases and remain fully available to your account - As the Bedrock model portfolio evolves, eligibility criteria may be reviewed

Anyone have any luck with this? Still having this error with 4.7 & 4.8.

OK, good news: after some trial and error, based on https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws I replaced my existing ~/.env for AWS Bedrock with Claude Platform on AWS environment variables: created a new account registration via AWS Marketplace -> Claude Console + new API key, back and forth between AWS Claude Platform Console and Claude Console), and it worked, i.e. now my Claude code is powered by Claude Platform on AWS, Opus 4.7 is there as the default. The billing is still on AWS so all our credits should still work; thought granular console via Claude Workspace is big weird, I can only see / create one workspace, but I still can create more API keys, so at least I have segregation for different projects or by different team members. Next see how stable / rate limiting it might be, and how the billing / cost splitting works.

It does work for me for Claude Platform on AWS, but it has a separate bill (it counts for AWS marketplace on AWS bills instead of AWS Bedrock) which could not use my current AWS credit.

Adding our data point — confirming this is still active for Opus 4.8 as of 2026-06-08 (~3 hours ago and just now).

Environment

• Region: us-east-1
• Failing models: us.anthropic.claude-opus-4-8, global.anthropic.claude-opus-4-8, us.anthropic.claude-opus-4-7
• Working on same account/region/credentials: us.anthropic.claude-sonnet-4-6, us.anthropic.claude-haiku-4-5 (no issues, normal latency)
• IAM tested two ways — console admin identity via CloudShell, and a scoped IAM user (AmazonBedrockFullAccess + explicit model ARNs). Identical 403 either way.
• AWS CLI 2.30.7

Control plane: AUTHORIZED on every signal

I also just hit this same issue

i have this same issue

I have the same issue.

same issue.

same issue

same issue

same