[provisioning bug] New account - all Bedrock quotas stuck at 0 TPM/0 RPM in eu-north-1

Regarding the "Buffer is not defined" error in the Quotas page: As to my understanding, this is typically a frontend UI glitch in the AWS Management Console. It generally happens when the web application attempts to parse an empty or unexpected quota payload and fails. It is purely a secondary symptom of the missing quotas.

While you wait for the support team to resolve the ⁠eu-north-1⁠ provisioning, you could check if quotas were provisioned in ⁠us-east-1⁠ or ⁠us-west-2⁠. However, it is highly likely that this restriction applies account-wide for the time being until Support clears it.

Based on the symptoms you're describing, this appears to be a provisioning issue with your new AWS account where the default Amazon Bedrock quotas were not properly initialized in the eu-north-1 region.

For new AWS accounts, Amazon Bedrock should automatically provision default service quotas for supported models in each region. The fact that you're seeing 0 TPM/0 RPM across all models, "No quotas found" in the console, and immediate throttling errors on your first request indicates the quota initialization process did not complete successfully for your account.

Since you've already opened an AWS Support case, that is the correct path forward. The support team will need to investigate why the automatic quota provisioning failed and manually provision the appropriate default quotas for your account in eu-north-1. This is not something that can be resolved through the standard Service Quotas console or by requesting quota increases, as the base quotas need to be established first.

In the meantime, you may want to verify if quotas are properly provisioned in other AWS regions where Bedrock is available. If they are, you could temporarily use those regions while the support team resolves the eu-north-1 provisioning issue. However, the support case is the definitive way to get this resolved, as it requires AWS intervention to correct the account provisioning state.

The console error "Buffer is not defined" you're seeing is likely a secondary symptom of the missing quota data rather than the root cause of the problem.