- Newest
- Most votes
- Most comments
Thank you for the detailed description. What you're experiencing is a known provisioning behavior with new AWS accounts and Amazon Bedrock, particularly in EU regions where additional compliance and data residency controls apply.
For new AWS accounts, Bedrock quotas are not automatically provisioned at the documented default values. Instead, accounts typically start with zero or very low quotas until AWS reviews and approves your use case. This is especially common when requesting access to high-capability models like Claude Opus and Sonnet in EU regions, where additional verification steps may apply due to data residency requirements.
Regarding your support case, quota increase requests for Bedrock foundation models typically require review by the Bedrock service team, and the timeline can vary from 24-72 hours to several business days, depending on the requested capacity and region. The lack of consumption history on a new account can indeed slow the review process, but your detailed business justification and GDPR compliance requirements should help expedite it.
Here are some recommendations:
For your existing support case:
- If you haven't already, explicitly mention in your case that you have zero baseline quota (not requesting an increase above existing limits, but requesting initial provisioning)
- Emphasize the EU data residency requirement and that you specifically chose Bedrock for GDPR compliance
- Request a modest initial quota that aligns with your small internal user group (e.g., 10,000-50,000 TPM to start)
Alternative approaches while waiting:
- Consider starting with Claude Haiku, which typically has faster approval times and lower capacity requirements, to establish some usage history
- If you have an AWS account team or Technical Account Manager, engage them to help prioritize your case
- Ensure your support case is filed under the correct category (Service Limit Increase → Bedrock)
Timeline expectations: Based on similar cases, initial quota provisioning for new accounts typically takes 2-5 business days once the case is assigned to the Bedrock team. The fact that your case hasn't been assigned after 24 hours suggests it may still be in the initial routing queue.
Unfortunately, there isn't a self-service way to provision baseline quotas - all initial allocations for foundation models require AWS review and approval. This is by design to ensure responsible scaling and compliance with regional requirements.
If your case remains unassigned after 48 hours, consider updating it with additional urgency indicators or, if you have access to Business or Enterprise support, requesting case escalation.
Hello.
Since you've already contacted AWS support, I think all you can do is wait for their response.
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.
