I've gone back and forth with AWS Support several times about increasing the TPM quota for my Bedrock agents, but I keep receiving the same vague explanation about billing history. My company has been using roughly $300–$500 per month in AWS Activate credits for more than six months, so I expected that usage to count for something. A colleague at another startup using the same accelerator and credit program has had quota increases approved despite having a newer account, including EC2 regional limits and Bedrock model quotas. In my case, some smaller agent quotas were even removed after a couple of support exchanges, without any explanation. I'm trying to understand what is actually preventing the increase. Would calling AWS Support help, and is there a specific account or usage metric I should ask about?
2 Answers
I'd definitely try a phone call and request three specific things: the precise reason for the denial, the conditions required for approval, and an explanation for why the existing smaller quotas were removed. Ask the representative to document the answer in the case afterward so you have a clear record. The fact that another startup was approved doesn't necessarily mean the accounts are being evaluated identically, but AWS should still be able to tell you whether your account has a restriction or simply lacks the required history.
AWS quota decisions seem to depend heavily on account history, support level, and how AWS evaluates payment risk. A few hundred dollars in promotional credits may not be treated the same as a comparable amount paid directly, since there isn't much traditional payment history behind it. Different accounts can also receive different decisions depending on the review. I'd call support rather than relying only on tickets and ask for the exact criteria you need to meet—such as consistent usage, a payment-method change, or a specific account restriction. Also ask directly whether there is a hold or limitation on the account, since removing existing quotas is more concerning than simply denying an increase.
That makes sense, although it would be much easier to plan if AWS would state which requirement is missing instead of repeating the billing-history response.