- Newest
- Most votes
- Most comments
Yeah... I've had the exact same issue, the exact same error for more than 2 months now.
I've contacted support since day 1. Received a response 8 days later, with some troubleshooting steps. Back then, this error had a suffix saying something along the lines of "apply to get more quotas <link>" and the support employees or rather their copy pasted responses were mentioning outdated methods to troubleshoot the issue myself, such as navigating the old model access page. When I lost complete trust of whoever I was talking to, I demanded at least something concrete from their end, and the ticket went completely silent. I posted my situation on reddit, and an AWS employee reached out in the comments, telling me to send a DM of the ticket ID, to which I did.
A few weeks went by without anyone reaching out to the ticket, so I became frustrated enough to make a new ticket and basically carry over the overall history of my original ticket, hoping that it'll get seen. To my surprise I received a response in the new ticket after an entire month of silence, ensuring me that the details of my case were transferred to the correct team, while also giving me a heads up that it may take a while for a resolve. It has been 8 days since I received that response and I'm waiting patiently. Personally I believe this is some sort of anti-fraud security measure like you've mentioned, although in my case I wasn't really making rapid calls. I barely managed to spend around 40$ in credits using Claude models before my account got this error.
Hello.
As indicated in the answer at the following URL, it seems you need to contact AWS support.
Since you've already contacted AWS support, I think you'll just have to wait for a response.
https://repost.aws/questions/QUlhObzfbtShO_C7o8McwRLg/aws-bedrock-api-access-suddenly-blocked-for-organization-accounts-operation-not-allowed-error#AN8HEAN6q4S3C7885QxbezyQ
I've seen some posts like this, with problems similar to mine, however:
Some of them mention it being a payment identification problem (i made sure to update my registration and payment method on AWS), others say it's not a big deal and you just need to hit the support to get it working again, or even that it is a big deal and you need technical support (my level of support is basic, I've already contacted support and still haven't received a response and there's no sign of one), but none of these posts mention "ERROR 002" and I can't find anything helpful online, so i think it might be something somewhat new and specific (?).
Relevant content
- asked 14 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
Yes, i also belive it's an anti-fraud kind of thing, but they need a better way to confirm the user is valid other than just blocking everything up and not giving any single hint to solve it. I guess Cline might have done some rapid calls (but i only spent around $11 in like 5 days lol), but even the playground and cheaper models aren't working since then and i can't have the support feedback. I hope you get your problem solved, and the only thing i can do now is try to hit the support again without any perspective.