How to Set Up Amazon Q Developer in IntelliJ IDEA (Step by Step)
Amazon Q Developer still has a JetBrains plugin for IntelliJ, PyCharm and friends, but AWS is moving IDE coding features to Kiro. New Q 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, install the Amazon Q plugin from the JetBrains Marketplace (IDE 2024.3+), sign in with Builder ID or IAM Identity Center, then use chat and inline suggestions. New learners should start with Kiro — see Amazon Q Developer → Kiro.
Why this JetBrains lesson still exists
Java and Kotlin teams often live in IntelliJ. Some companies still have active Q Pro seats. You should know the Marketplace install — and the sunset dates — so you can 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 the AWS blog).
- Kiro: Successor IDE + CLI with specs, hooks, steering. For JetBrains, Kiro also documents an ACP path via JetBrains AI Assistant — follow current Kiro docs.
- 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.
- Use IntelliJ IDEA (or PyCharm / WebStorm / other JetBrains IDE) 2024.3 or later (AWS minimum).
- Settings → Plugins → Marketplace. Search Amazon Q. Install the official AWS plugin. Restart if asked.
- Click the Amazon Q icon on the side of the IDE.
- Builder ID: follow the browser sign-in. New Free Builder ID creation may already be closed — if sign-up fails, use Kiro or an existing company Pro seat.
- 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 Java/Kotlin file and open chat from the Amazon Q icon or navigation bar.
Settings
- Use Amazon Q in the IDE navigation bar to sign out, change profile, or open chat.
- Turn completions off in plugin settings if ghost text distracts you.
- Same plugin family works across supported JetBrains IDEs — install again in PyCharm if you switch.
Configuration
Example project note (keep secrets out)# Project note for Amazon Q (do not commit secrets) - Never paste AWS access keys, secret keys, or session tokens into chat. - Prefer IAM Identity Center or named profiles / instance roles. - For new AI coding setups, prefer Kiro (see site lesson) before investing in Q-only workflows.
- Never paste AWS access keys into chat. Use IAM Identity Center, instance roles, or named profiles.
- When you migrate, move project habits into Kiro steering files.
First task (only if you still use Q)
Explain this selected Java method in simple words. Suggest one JUnit 5 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 JetBrains 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. Minimum JetBrains version AWS lists?
2024.3.
3. What should new users install instead?
Kiro — see the Kiro lesson.
4. Two sign-in paths?
AWS Builder ID, or IAM Identity Center (company).
Save tokens and money
If you will migrate soon, spend time learning Kiro specs once instead of deep Q-only JetBrains habits that disappear in 2027.