Amazon Q Developer Pro - Monthly Limit Reached?

Hello.

Looking at the following GitHub issue, it seems that there are people in a similar situation to you.
Please check if you are signed in as an IAM identity center user.
https://github.com/aws/aws-toolkit-jetbrains/issues/5059

After subscribing, I think it was necessary to switch the Amazon Q Developer sign-in user in each IDE to the subscribed IAM Identity Center user.
https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-in-IDE-setup.html#setup-vscode

Thank you for sharing your experience with Amazon Q Developer Pro. I understand your frustration with hitting an unexpected limit. While the Pro tier is designed to provide access without hard monthly limits for general interactions, there are indeed some specific quotas for certain features that are not publicly listed.

The error message you're encountering suggests that you've reached an internal quota for a specific type of interaction (GenerateAssistantResponse). This is likely an internal limit set by AWS to ensure fair usage and optimal performance for all subscribers.

Unfortunately, there isn't a straightforward way for users to increase these internal quotas themselves. The Pro tier does offer higher usage limits compared to the Free tier, but it appears that there are still some restrictions in place.

Given that you're consistently hitting these limits and it's impacting your work, here are a few suggestions:

1. Wait for the next billing cycle: Your limits should reset at the start of the new billing period.

2. Optimize your usage: Try to identify if there are any inefficiencies in your current usage that could be optimized to stay within the existing limits.

3. Contact AWS support or your account representative: If you have a paid support plan or an account representative, reach out to discuss your specific needs and see if there's a possibility for a limit increase.

4. Provide feedback: AWS is generally receptive to feedback about increasing limits for power users. Even if you can't get an immediate resolution, your input could influence future improvements to the service.

5. Consider enterprise-level solutions: If Amazon Q Developer is crucial for your business operations, you might want to explore if there are enterprise-level solutions that could better accommodate your usage patterns.

In the meantime, you could try breaking down your prompts into smaller, more focused requests. This might help you continue working within the current limits while a more permanent solution is found.

We apologize for the inconvenience this is causing to your development process. Rest assured that AWS is continually working to improve their services based on user feedback and experiences like yours.
Sources
Amazon Q Developer Pro Tier - Reached Limit - Not even being charged for $0.03 to continue developing | AWS re:Post
Q Developer Pro subscription limits? | AWS re:Post