Action Required: Amazon Bedrock Service Suspended - what action??
We received an email titled "Action Required: Amazon Bedrock Service Suspended". It says our access to Bedrock was suspended because AWS "could not validate important details" about our account, and that all other AWS services remain unaffected.
That last part is accurate. Everything else on the account works normally, including SES, which was granted production access the evening before this suspension notice arrived.
The problem is the title. It says "Action Required" but names no action we can take. It asks us to contact Support and "provide any supporting documentation that may help" - without saying what was invalid, which detail failed validation, or which document would fix it. So we are guessing, which is the slowest possible path for everyone.
WHAT WE SEE
Every Bedrock invocation in eu-central-1 fails with:
400 Error 002: Access to Bedrock models is not allowed for this account
Last success and first failure are about 16 hours apart. Nothing changed on our side in between - no new IAM policy, no new region, no change in usage.
WHAT WE USE IT FOR
We are a small German consultancy, located in Cyprus. Our platform helps certified business consultants prepare mandatory reports for a German federal subsidy programme. We call Claude models through Bedrock using the EU inference profile, and we are on Bedrock specifically for data residency: our data processing agreement names Frankfurt as the processing location, and Anthropic's own API offers only US and global inference.
Usage is low and steady - a few hundred invocations since February, roughly 25 to 30 per month. No batch jobs, no high-volume traffic.
WHAT WE HAVE ALREADY DONE
Opened a case as the root user under Account and Billing, category Account Reinstatement, describing all of the above and offering company registration, VAT registration, proof of address and payment method verification the same day they are requested. We have not opened another account.
MY QUESTIONS
-
Is there anything the account owner can do proactively, or is waiting for the verification team the only path? If there is a self-service step - re-submitting a payment method, confirming a phone number, anything - I would rather do it now than wait to be asked.
-
Does anyone know which account detail this check actually looks at? The email is vague, and I would like to send the right document with the first reply instead of the third.
-
Realistically, how long does this queue take? Reports here range from under a day to two weeks. Knowing whether to expect days or weeks changes what we tell our customers.
-
Is it a coincidence that this arrived the morning after an SES production access approval on the same account? It looks like the same account review concluded differently for the two services.
Happy to provide the account ID and case ID privately to anyone from AWS who can look at it.
- Language
- English
asked a month ago166 views
- Newest
- Most votes
- Most comments
Hi there.
I apologize for the trouble you're experiencing with the Amazon Bedrock service being suspended.
I've located your case and shared your sentiments internally. Once our Support team completes their review, correspondence will be shared via our Support Center: http://go.aws/support-center.
— Roman Z.
AWS Support came back within a day. Summary, in case it helps anyone hitting the same error:
- The account is confirmed to be "in good standing" — no issue with payment method, phone verification or account identity.
- There is no self-service step. The review has to be completed on their end.
- No timeline given. It has been escalated to the Bedrock team.
So the suspension is not something the account owner triggered or can undo. If you are seeing "Error 002: Access to Bedrock models is not allowed for this account" while everything else in your account works normally, opening an Account Reinstatement case appears to be the only path.
Our production workload is running on a fallback in the meantime, so there is no outage — but the fallback processes data outside the EU, which is the reason we were on Bedrock in the first place.
Question to anyone who has been through this: has this happened to you with an otherwise healthy account, and how long did it take to be restored? Any data point helps.
Case 178885201800211
answered a month ago
Update, one week on: still suspended, still no response on the support case (178885201800211, opened 2026-09-08).
The error is unchanged when calling bedrock-runtime in eu-central-1 against an eu.anthropic.* inference profile:
Error 002: Access to Bedrock models is not allowed for this account
Every other service on the account works normally, SES included — production access for SES was in fact granted the day before the Bedrock suspension arrived, after an account review. Usage has been low and steady since February, around 25-30 invocations a month, no batch traffic.
Two questions to anyone who has been through this:
- Did "Error 002" resolve on its own for you, or did it take a specific document or action on the account before anything moved?
- Is there a way to get a stalled Account Reinstatement case looked at that does not involve opening a second case?
Happy to add detail if that helps someone recognise the pattern.
answered a month ago
