Amazon Q Pro subscription not recognized in VS Code due to Builder ID and GitHub conflict

As of March 2026, AWS Builder ID supports Sign-in with GitHub. This is the key to linking your subscription without needing a deleted AWS Console account.

"As noted in the AWS Weekly Roundup from March 16, 2026, AWS Builder ID now natively supports Sign-in with GitHub. This update was specifically designed to resolve credential conflicts for developers using Amazon Q."

source: https://www.westloop.io/post/aws-builder-id-now-supports-sign-in-with-github-and-amazon

1. Link GitHub to your Builder ID

Instead of creating a new ID, go to the "AWS Builder ID profile page" -> https://profile.aws.amazon.com . Choose "Sign in with GitHub".

• Use the same GitHub account you used for the purchase.
• Since the emails match, AWS will prompt you to link this login to your existing Builder ID profile. Once linked, the Pro subscription associated with your GitHub identity becomes available to your Builder ID.

2. Reset VS Code Authentication

VS Code often caches the "Free Tier" token. You must force a refresh:

• In VS Code, click the Amazon Q icon in the sidebar.
• Select Sign Out from the menu (or the person icon at the bottom).
• Click Connect to Amazon Q and select AWS Builder ID.
• In the browser window that opens, specifically choose "Sign in with GitHub".

3. If you still cannot access the subscription (Support Access)

Since you cannot log in to the AWS Console, use the AWS Center - Contact Us form.

• Select "Billing or Account Support".
• You do not need to log in to submit this form. Provide your GitHub email and explain that you have an orphaned Amazon Q Pro subscription on a GitHub identity that needs verification.

In short: Do not try to "move" the sub. Instead, use the "Sign in with GitHub" option inside the Builder ID login flow to merge the two.

Based on the information available, here are some steps to help resolve your subscription recognition issue:

First, verify that your Amazon Q Developer Pro subscription is actually active. There can be delays in subscription activation, particularly if you were subscribed as part of a group (which can take up to 24 hours).

If you recently purchased the Pro subscription, try signing out of Amazon Q completely in VS Code and then signing back in. This refresh can sometimes resolve subscription recognition issues when switching between tiers.

Since you're experiencing a conflict between your GitHub login (which has the subscription) and your Builder ID (which VS Code is defaulting to), you may need to ensure that your access to the Amazon Q Developer Pro managed application hasn't been inadvertently revoked or that the managed application itself wasn't deleted.

While waiting for the subscription issue to be resolved, you can continue using Amazon Q's Free tier by signing in with your Builder ID.

However, the specific scenario you're describing—where a Pro subscription purchased through GitHub needs to be linked to or transferred to a Builder ID—requires account-level assistance that goes beyond standard troubleshooting. Since you cannot access AWS Support through the console due to your deleted AWS account, I recommend reaching out to AWS Support through alternative channels or contacting Amazon Q Developer support directly to help link these identities or transfer your subscription appropriately.
Sources
Users unable to use their subscription in the IDE - Amazon Q Developer