Can't access any model on Bedrock, even though i have a free trial, 0 quota to everything

Hello.

I saw a question about a similar situation to yours about a month ago.
It seems that communication with AWS support is necessary to resolve this issue, and if you have already contacted them, you will just have to wait for their response.
https://repost.aws/ja/questions/QU3vGNsL2TS1OTkcWjDwcN9w/amazon-bedrock-throttlingexception-on-all-models-account-shows-0-applied-quota

Also, please note that Bedrock quota requests may be rejected depending on the use case and usage, as described in the following documentation.
https://docs.aws.amazon.com/bedrock/latest/userguide/quotas-increase.html

Due to overwhelming demand, priority will be given to customers who generate traffic that consumes their existing quota allocation. Your request might be denied if you don't meet this condition.

Incidentally, while model access is mentioned in other answers, as stated in the following document, model access is enabled automatically, so you do not need to do anything.
https://docs.aws.amazon.com/bedrock/latest/userguide/model-access.html
https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-bedrock-automatic-enablement-serverless-foundation-models/

Amazon Bedrock now provides immediate access to all serverless foundation models by default for users in all commercial AWS regions. This update eliminates the need for manually activating model access, allowing you to instantly start using these models through the Amazon Bedrock console playground, AWS SDK, and Amazon Bedrock features including Agents, Flows, Guardrails, Knowledge Bases, Prompt Management, and Evaluations.

For new accounts or accounts with limited AWS service usage history, both Bedrock model access and default quotas (TPM/RPM) may be unavailable or reduced. This is expected behavior — not a provisioning bug — and is subject to AWS's internal account eligibility review process based on the account's usage history and other factors. This cannot be resolved by support "provisioning quotas manually." Customers in this situation should contact AWS Support, who will evaluate eligibility and work to restore access and appropriate quota levels where possible.

This is a known provisioning issue that affects some new AWS accounts. The 0 applied quota across all models and regions, including Amazon's own models, is not standard behaviour — it indicates your account's Bedrock service quotas were not provisioned correctly at account creation.

Two separate things to fix:

1. Model access (do this first) Console → Amazon Bedrock → Model access → Enable the models you need. This is separate from quotas and must be done before any invocation works.

2. The 0 quota issue This requires AWS Support to manually provision quotas at account level. You already have an open case — reply to it with this specific information:

"All Bedrock applied quotas show 0 across all regions including Amazon native models. AWS default quotas are visible in Service Quotas but effective account-level quotas remain at 0. This appears to be an account provisioning issue, not a standard quota increase request. Please provision the default Bedrock service quotas for this account."

Being specific about the account provisioning framing gets it escalated to the right team faster than a generic quota increase request.

What to expect: Once AWS Support provisions the quotas, they typically apply within a few hours. You won't need to resubmit your Claude quota increase requests — those will be processed against the now-provisioned limits.

This issue has been reported by several other new accounts recently — you're not alone.

Ref: How do I enable access to Anthropic Claude models on Amazon Bedrock?

For new accounts or accounts with limited AWS service usage history, both Bedrock model access and default quotas (TPM/RPM) may be unavailable or reduced. This is expected behavior — not a provisioning bug — and is subject to AWS's internal account eligibility review process based on the account's usage history and other factors. This cannot be resolved by support "provisioning quotas manually." Customers in this situation should contact AWS Support, who will evaluate eligibility and work to restore access and appropriate quota levels where possible.