Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

AWS Transform failed in Visual Studio despite ACTIVE "Amazon Q Developer Pro" subscription (Quota Exceeded / 402)

0

Hi community,

I am trying to use AWS Q Code Transformation ("AWS Transform") inside Visual Studio 2022 to upgrade a .NET application.

The job starts processing but quickly fails with a ServiceQuotaExceededException and a 402 Status Code.

The Error Log:

Plaintext Job has failed, Id is [GUID] Reason: Error Code: 500 Error Message: Metering API error (ServiceQuotaExceededException): An error occurred (ServiceQuotaExceededException) when calling the PublishMeteringEvent operation: metering service exception Service returned error code ServiceQuotaExceededException (Service: ElasticGumbyMetering, Status Code: 402) My Configuration & Troubleshooting:

Subscription: I have purchased Amazon Q Developer Pro. The status in the AWS Console is explicitly ACTIVE.

User Assignment: My user is assigned to this subscription in the Identity Center.

Authentication: I am logged into the AWS Toolkit in VS via IAM Identity Center (SSO), not via Builder ID.

Region: My SSO and Toolkit are correctly configured to the same region.

Refresh: I have tried signing out and signing back in to the AWS Toolkit to refresh the token.

The Issue: Despite having the Pro subscription (which should allow up to 1M LOC), the service seems to treat my user as Free Tier (Quota Exceeded).

Has anyone experienced a delay between the subscription becoming "Active" and the IDE recognizing the new quota? Is there a specific step to force the "Metering Service" to recognize the Pro license?

Thanks

Topics
Machine Learning & AIMigration & Modernization
Tags
AWS Transform
Language
English

asked 7 months ago108 views

1 Answer
1

When experiencing a ServiceQuotaExceededException with AWS Transform in Visual Studio despite having an active Amazon Q Developer Pro subscription, there are several potential issues to consider.

First, it's important to understand the quotas that apply to .NET transformations with Amazon Q in the IDE:

  • Lines of code per job: Maximum 100,000 lines of code
  • Concurrent jobs: Limited to 1 job per user and 2 jobs per AWS account

For Java transformations, there are different tiers (Free vs Pro) with different quotas, but for .NET transformations, the documentation doesn't indicate separate tier limits like it does for Java.

To troubleshoot this issue:

  1. Check if you're exceeding the 100,000 lines of code limit for .NET transformations.

  2. Verify that you don't have other transformation jobs running concurrently (limit is 1 per user).

  3. Confirm that your organization isn't exceeding the 2 concurrent jobs per AWS account limit.

  4. Check the IDE logs for more detailed information:

  • In Visual Studio, go to View > Command Palette
  • Enter "Amazon Q: View Logs" to open the logs
  • Use Ctrl+F to search for transformation-related errors

  1. If you're using AWS Transform specifically (rather than Amazon Q Developer directly), ensure you've properly enrolled users following the AWS Transform documentation.

  2. There could be a delay between subscription activation and recognition in the IDE, so waiting some time and trying again might help.

If these steps don't resolve the issue, contact AWS Support and include your transformation job ID in the support case for more targeted assistance.
Sources
Transforming .NET applications with Amazon Q Developer - Amazon Q Developer
Transforming Java applications with Amazon Q Developer - Amazon Q Developer
Port your .NET Framework applications to Linux with AWS Transform for .NET | Microsoft Workloads on AWS
Troubleshoot Amazon Q Developer code transformation failures | AWS re:Post

answered 7 months ago

AWS
EXPERT

reviewed 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content