How to Set Up Amazon Q Developer in Visual Studio (Step by Step)
On Windows, Amazon Q Developer rides inside the AWS Toolkit for Visual Studio. Support for Q IDE plugins ends 30 April 2027. New Free Builder ID / new Q subscriptions were restricted from 15 May 2026. Prefer Kiro for new setups.
In short: Visual Studio 2022 17.7+ on Windows only, enable Amazon Q from the AWS Toolkit Getting Started UI, sign in with Builder ID or IAM Identity Center, then use chat/inline until EOS. New learners: start with Kiro.
Why this Visual Studio lesson still exists
.NET teams often stay in Visual Studio. Some orgs still have Q Pro seats and need the Toolkit path for a while. You should know the real install steps — and when to leave for Kiro.
What you need
- Windows + Visual Studio: AWS docs: only Visual Studio for Windows. Minimum VS 2022 version 17.7 (all 2022 editions).
- AWS Toolkit for Visual Studio: Amazon Q is enabled from Toolkit → Getting Started.
- Eligible sign-in: Existing Builder ID / Pro seat, or company IAM Identity Center. New Free Builder ID creation may already be blocked.
- Kiro for new work: Successor path with newer models and specs.
How setup flows (existing access)
Install steps
- New to AWS AI coding? Prefer Kiro instead of starting on Q.
- Install or update Visual Studio 2022 (17.7+) on Windows. Check Help → About.
- Install/update the AWS Toolkit for Visual Studio from the Visual Studio Marketplace / Extensions.
- Main menu: Extensions → AWS Toolkit → Getting Started.
- In the Amazon Q section, choose Enable.
- Builder ID (Free Tier section): Sign up or Sign in → confirm browser portal → return to Visual Studio when authorised.
- IAM Identity Center (Professional Tier): fill Profile Name, Start URL, Profile Region, SSO Region from your admin → Connect → browser authorize → pick Q profile if asked.
- Open Amazon Q chat from the IDE navigation / chat panel and try one small C# question.
Settings
- Change Q Developer profile from the Amazon Q navigation entry or chat overflow → Change Q Developer Profile.
- You cannot use a plain IAM user/role as the IDE identity — Builder ID or IAM Identity Center only (AWS docs).
- If Toolkit and Q menus look different after an update, follow the current “Authenticating in Visual Studio” page in AWS docs.
Configuration
Reminder note# Visual Studio + Amazon Q (legacy path) - Windows only for Amazon Q in Visual Studio (AWS docs). - Enable Amazon Q from Extensions → AWS Toolkit → Getting Started. - New Free Builder ID / new Q subscriptions restricted from 15 May 2026; IDE plugins EOS 30 Apr 2027.
- Never paste long-term AWS access keys into chat.
- Finish any .NET Q code transformation jobs before 30 Apr 2027 if you depend on them.
First task (only if you still use Q)
Explain this selected C# method. Suggest one xUnit test idea. Do not ask for AWS credentials.
| Fact | Detail |
|---|---|
| OS | Windows only for Q in Visual Studio |
| EOS | 30 April 2027 for Q IDE plugins |
| New Free sign-ups | Restricted from 15 May 2026 |
| Successor | Kiro |
- Company GenAI policy first.
- Do not paste customer data or connection strings into chat.
Quick quiz
1. Does Amazon Q in Visual Studio support Mac?
No — AWS documents Visual Studio for Windows only.
2. Minimum VS version?
Visual Studio 2022 version 17.7.
3. Where do you enable Q?
Extensions → AWS Toolkit → Getting Started → Enable Amazon Q.
4. When do IDE plugins end?
30 April 2027.
Save tokens and money
Prefer short questions about one method. Migrate learning time to Kiro if your seat will end.