I have AWS startup credits, but I'm unable to use them effectively. A modest request for 32 vCPUs was denied, and although I was told that Anthropic models had been enabled for my account in Amazon Bedrock, the console still reports that model access is blocked. The same issue appears to affect the other Bedrock models as well. Support has repeatedly said that the restrictions were removed, but nothing actually changes, and responses can take weeks. Has anyone found a reliable way to resolve quota and Bedrock access problems like this?
2 Answers
If this is a throwaway or newer account, one workaround people use is to launch a few tiny instances for a short period in each region where they need capacity, then reopen the quota request. It’s not an official guarantee, but some teams report that this helps establish account usage before asking for a larger quota. A cloud distributor or partner may also be able to handle these account and quota issues on your behalf.
For Bedrock, check the model access page in every region you plan to use and verify that the request is enabled for the specific model IDs, not just the provider generally. Access can remain blocked even after support says it was approved, so include the exact region, model ID, account ID, and screenshots in the case. If support keeps marking the case resolved without changing the account, ask them to confirm the backend entitlement and quota values explicitly.
I’ve already opened cases and provided the case IDs through several support channels. The recurring problem is that support says the restrictions are fixed, but the console and API still behave exactly the same. I also tried newer Anthropic models, but I don’t see much value in using the older ones because they feel too limited.