How to Set Up Amazon Q Developer in VS Code (Step by Step)
Amazon Q Developer still has a VS Code extension for chat and inline suggestions, but AWS is moving IDE coding features to Kiro. New Q Developer Free Builder ID sign-ups were blocked from 15 May 2026; IDE plugins are supported until 30 April 2027. Prefer Kiro for new setups.
In short: if you already have Q Developer access, you can install the Amazon Q extension, sign in with Builder ID or IAM Identity Center, and use chat/inline until EOS. New learners should start with Kiro — see Amazon Q Developer → Kiro.
Why this lesson still exists
Many teams still have Q Developer Pro seats and need the VS Code plugin for a while. You should know how to install it — and know the sunset dates so you plan the move to Kiro.
What is ending vs what continues
- Q Developer IDE plugins: VS Code, JetBrains, Visual Studio, Eclipse — end of support 30 April 2027.
- New Q Free / new subscriptions: New Builder ID Free account creation and new Q subscriptions blocked from 15 May 2026 (existing Pro can still add users on active subs — re-check AWS blog).
- Kiro: Successor IDE + CLI: specs, hooks, steering, newer models. Start here if you are new.
- Q in AWS Console: Not part of this IDE sunset — Console Q continues.
How setup flows (existing access)
Install steps
- New to AWS AI coding? Stop here and follow Set up Kiro instead.
- VS Code 1.85.0 or later (Help → About).
- Extensions view (Ctrl+Shift+X): search Amazon Q / Amazon Q Developer. Install the official AWS extension.
- Click the Amazon Q icon in the Activity Bar.
- Builder ID: follow the browser sign-in (free tier historically did not need an AWS account — new Free Builder ID creation may already be closed).
- Company: choose company/IAM Identity Center, paste the Start URL and Region your admin gave you.
- If multiple Q profiles appear, pick the one your admin named.
- Try inline suggestions in a code file and open chat from the Amazon Q icon or status entry.
Settings
- Use the Amazon Q status / navigation bar entry to sign out, change profile, or open chat.
- Turn completions off from the extension settings if ghost text distracts you.
- Workspace rules / customize options vary by version — open the extension’s contribution settings in VS Code and read the current AWS doc page “Installing Amazon Q in your IDE”.
Configuration
Example workspace note (keep secrets out)# Workspace rules (example) - Prefer AWS SDK v3 / current boto3 patterns - Never hard-code access keys; use profiles or IAM roles - Run unit tests before suggesting a commit
- Never paste AWS access keys into chat. Use IAM Identity Center, instance roles, or named profiles.
- For long-term project rules, prefer migrating those habits into Kiro steering files when you move.
First task (only if you still use Q)
Explain this selected function in simple words. Suggest one test. Do not print or request cloud credentials.
| Situation | What to do |
|---|---|
| Brand-new student (Oct 2026+) | Install Kiro, not Q |
| Existing Q Pro / active seat | You may keep using the VS Code plugin until 30 Apr 2027 |
| Need newest models / specs | Use Kiro |
| Only need AWS Console help | Q in Console still fine |
- Finish Java/.NET Q code transformations before 30 Apr 2027 if you rely on them.
- Follow your company’s AWS GenAI policy.
Quick quiz
1. When do Q Developer IDE plugins end support?
30 April 2027.
2. What should new users install instead?
Kiro (kiro.dev) — see the Kiro lesson.
3. Two VS Code sign-in paths?
AWS Builder ID, or IAM Identity Center (company).
4. Is Q in the AWS Console ending with the IDE plugins?
No.
Save tokens and money
If you are migrating soon, spend tokens learning Kiro specs once instead of deep Q-only workflows that disappear in 2027.