New account: Bedrock returns "Operation not allowed" / NOT_AUTHORIZED for all models in all regions after 9+ days

Hi,

Thank you for the detailed write-up — this is very helpful for troubleshooting. Based on what you've described, this is not a permissions, payment, or regional issue. This is an account-level Bedrock authorization hold that sometimes affects newly created AWS accounts.

What's Happening

Your API output tells the full story:

• authorizationStatus: NOT_AUTHORIZED — Your account has not been authorized for Bedrock model access
• agreementAvailability: AVAILABLE — The Marketplace agreement is ready
• entitlementAvailability: AVAILABLE — The model entitlement exists
• regionAvailability: AVAILABLE — The model is available in your Region

Everything is green except the account-level authorization. The Bedrock console message "Your account verification is in progress" confirms this — AWS has an internal verification step for Bedrock access on new accounts that is separate from EC2 verification or billing activation.

Why This Happens

AWS applies additional verification checks for certain services (including Bedrock) on newly created accounts. This is a fraud/abuse prevention measure. Unlike EC2 verification, Bedrock authorization is a separate internal process and cannot be triggered manually by the customer. Having active billing, running EC2 instances, or having correct IAM permissions does not bypass this hold.

What You Can Do

1. Escalate your existing Support case — Since you've had a case open for 9+ days with only automated responses, reply to the case and request an escalation. Specifically mention:

   • The authorizationStatus: NOT_AUTHORIZED output from get-foundation-model-availability
   • That the console shows "account verification is in progress" for over 2 weeks
   • That this is blocking you from completing the Bedrock tutorial and using your $20 credit
   • Request the case be routed to the Bedrock service team, not general support

2. Use the "Contact Us" option in the AWS Console — If your current case isn't progressing, open a new case under Account and Billing → Account (not Technical Support) and explain that your account has not been authorized for Amazon Bedrock despite being active for over 2 months.

3. Try the AWS re:Post "Ask an Expert" option — AWS staff monitor re:Post and can sometimes flag account-level issues internally.

What Won't Help (Saving You Time)

• Launching/terminating EC2 instances — You've already confirmed this doesn't trigger Bedrock authorization
• Switching IAM users/roles — The block is at the account level, not the identity level
• Trying different models or Regions — NOT_AUTHORIZED applies account-wide
• Completing the Anthropic FTU form — This is only relevant after account authorization is granted

Relevant Documentation

• Request Access to Amazon Bedrock Models
• Troubleshooting Amazon Bedrock API Error Codes
• Set Up Amazon Bedrock

Unfortunately, there is no self-service way to manually trigger Bedrock account authorization — it requires AWS to complete the internal verification on their end. The best path forward is escalating your Support case and being specific about the NOT_AUTHORIZED status.

Hope this helps, and sorry you're dealing with this delay!