wbmeet

How to install and use Amazon Q Developer in VS Code: sign-in and first suggestions

Install the Amazon Q extension, finish Builder ID or company SSO sign-in, then get your first inline suggestion or chat reply in your own repo.

The first hour with Amazon Q Developer in VS Code usually breaks on the wrong extension, picking Builder ID versus company IAM Identity Center, or never seeing inline completions and chat connect. Install from official docs, authenticate in the browser, then trigger one suggestion or ask one question in a repo you own.

The query is how to install and use Amazon Q Developer in VS Code. This page follows AWS docs at docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-in-IDE-setup.html, the Builder ID getting-started guide, and Marketplace item AmazonWebServices.amazon-q-vscode. It is an AWS IDE assistant, not this site’s meeting product. For a short huddle to review a diff, open a room on wbmeet; see how to create and join a room.

Install extensionSign inSuggestions & chat

Check which sign-in path you can use

Amazon Q Developer is AWS’s AI assistant in the IDE: inline code suggestions (the former CodeWhisperer capability), sidebar chat, explanations, and refactors. The VS Code extension is published by Amazon Web Services as AmazonWebServices.amazon-q-vscode. Personal free use goes through AWS Builder ID (a personal profile; no full AWS account; browser email or Google sign-in). Employees on Amazon Q Developer Pro choose Company account and SSO through IAM Identity Center with an admin-provided Start URL and AWS Region.

2 auth
Builder ID or IAM Identity Center
0 IAM
No IAM user/role sign-in in IDE
1 ext
Marketplace: Amazon Q

First hour: install, sign in, get suggestions or chat

  1. 1

    Install Amazon Q from the Marketplace

    Open VS Code. Cmd+Shift+X or Ctrl+Shift+X. Search Amazon Q, publisher Amazon Web Services, Install. Or Quick Open (Cmd+P / Ctrl+P): ext install AmazonWebServices.amazon-q-vscode. Reload if asked. The Amazon Q icon appears in the Activity Bar.

  2. 2

    Pick a sign-in method and finish in the browser

    Click the Amazon Q icon. For personal projects choose Builder ID and create or sign in to AWS Builder ID in the browser (email or Google; see AWS Sign-In docs). For company Pro choose Company account, enter the IAM Identity Center Start URL and AWS Region from your admin, Continue, complete SSO in the browser, return to VS Code. Do not paste IAM Access Keys into the extension.

  3. 3

    Open your repo and test inline suggestions

    File → Open Folder on a project you can roll back. Open a source file and type normally. After a few seconds gray inline completions should appear; Tab to accept, Esc to dismiss. If nothing appears, check the Amazon Q connection status and free-tier quota.

  4. 4

    Ask your first question in chat

    Open the Amazon Q chat panel. Start read-only: “Where is the main entry point in this repo?” or “Explain the function in the open file.” If you want edits, say “suggest a diff only; wait for my approval.” Do not paste keys, customer data, or production connection strings. The first-hour goal is confirming both suggestions and chat respond.

# First hour · Amazon Q Developer in VS Code · as of 2026-09
# 1. Extensions → Amazon Q (publisher Amazon Web Services)
#    id: AmazonWebServices.amazon-q-vscode
# 2. Activity Bar → Amazon Q → Builder ID (personal)
#    OR Company account + Start URL + Region (Pro / org)
# 3. Open your repo. Type in a source file → wait for inline ghost text
# 4. Amazon Q chat: "Where is the main entry point in this repo?"
# Do not paste IAM access keys. Free Builder ID has usage limits.

Sign-in paths, features, pitfalls

PathWhat official docs sayFirst-hour note
Personal freeAWS Builder ID, no AWS accountComplete email/Google in browser
Company ProIAM Identity Center + Start URL + RegionAsk admin for URL and region
Not supportedIAM user / IAM role in IDEDo not paste Access Keys
Inline suggestionsGhost text while typing; Tab to acceptConfirm auth and quota first
ChatActivity Bar Amazon Q panelStart with a read-only question
01

Install works but sign-in loops

Often a blocked browser pop-up or unverified Builder ID email. Allow VS Code to open external links, finish login in the default browser, then switch back.

02

Company account missing Start URL

Start URL and Region come from IT via the Amazon Q subscription console. Personal Builder ID does not need them. Mixing paths breaks SSO.

03

No inline suggestions at all

Check supported file types, Amazon Q Connected status, and free-tier limits. View → Output → Amazon Q for errors.

Official IDE setup: Marketplace Amazon Q → Activity Bar icon → Builder ID or Company account → browser auth → chat or wait for inline suggestions. Pricing and limits follow aws.amazon.com/q/developer/pricing.

Builder ID ≠ AWS console account
Builder ID is a personal IDE identity. It cannot open the AWS Management Console or carry IAM roles. Console Q needs IAM Identity Center.
Free tier has limits
Personal Builder ID free tier caps suggestions and chat usage. Beyond that you need Pro or org IAM Identity Center.
This is not a meeting-product guide
Only Amazon Q’s first hour. Short whiteboard call: wbmeet or when not to open another heavy meeting app.

Questions worth checking

Do I need an AWS account?

Not for personal free use—AWS Builder ID is enough. Company Pro uses IAM Identity Center from your org admin, not IAM Access Keys in the IDE.

Can I sign in with an IAM user Access Key?

No. AWS docs say IDE Amazon Q does not support IAM principals or IAM roles. Use Builder ID or IAM Identity Center SSO.

How are inline suggestions different from chat?

Inline suggestions appear as gray ghost text while you type; Tab accepts. Chat lives in the Activity Bar panel for explanations and questions. Both need authentication first.

Must the first task touch production code?

No. Start with a read-only question or inline completion in a small file. After it works, make one reversible change and review every line.

Start a free meeting