Amazon Q Developer to Kiro: How to Set Up Kiro (Step by Step)
AWS is moving its coding assistant from the Amazon Q Developer IDE plugins to Kiro. Kiro is an AI coding IDE and CLI built for spec-driven development: you write what you want, it plans, builds and checks.
In short: Q Developer IDE plugins end support on 30 April 2027, and new Q Developer sign-ups stopped on 15 May 2026. Download Kiro from kiro.dev, import your VS Code profile, and sign in.
Why move to Kiro
New AWS coding features and the latest models now land in Kiro, not in the Q Developer plugins. Starting with Kiro now avoids a forced move later. Q Developer inside the AWS Console is not affected.
What changes
- Q Developer IDE plugins: VS Code, JetBrains, Visual Studio, Eclipse. Supported until 30 April 2027; existing users keep access till then.
- Kiro IDE: a standalone editor built on VS Code with agent chat, inline suggestions, specs, hooks and steering.
- Kiro CLI: Kiro in the terminal. The Q Developer CLI was renamed to Kiro.
- Specs: structured requirements Kiro uses to plan, build and verify.
- Hooks: automatic actions on events like file save or commit (run tests, update docs).
- Steering files: project files that tell Kiro your architecture and rules.
How setup flows
Install steps
- Go to kiro.dev and download Kiro IDE for your system. Install it.
- On first start, Kiro asks to import your VS Code profile. Accept to bring extensions, settings and keybindings.
- Sign in with GitHub, Google, AWS Builder ID, or IAM Identity Center (company accounts).
- Open your project folder.
- Terminal users: install Kiro CLI with the command on kiro.dev, then sign in through its login flow.
Which path for your IDE
| You use Q Developer in… | Move to |
|---|---|
| VS Code | Kiro IDE (imports your VS Code profile) |
| IntelliJ, PyCharm, WebStorm | Kiro CLI, added as an agent in JetBrains AI Assistant (ACP) |
| Visual Studio or Eclipse | Kiro IDE or Kiro CLI (no native plugin) |
| Q Developer CLI | Kiro CLI (renamed) |
| Q in the AWS Console | No change |
Settings and configuration
- Steering files: add your stack and rules (for example “Python 3.12, pytest, boto3, never hard-code AWS keys”). Kiro keeps project config in the
.kirofolder. - Terminal allow/deny list: allow safe commands (tests, lint) and deny risky ones (deletes, deploys).
- Hooks: start with one: run tests on save.
- Admins: the Q Developer console is now the Kiro console; manage users there.
First task (spec-driven)
- Ask Kiro: “Build a function that validates an AWS S3 bucket name, with tests.”
- Choose to create a spec. Read the requirements and plan it writes. Fix anything wrong.
- Approve. Kiro builds the code and tests.
- Run the tests yourself and review the diff.
- Java upgrades and .NET porting (Q code transformation) also end on 30 April 2027. Finish those jobs before then.
- AWS keys: use IAM Identity Center or AWS profiles. Never paste access keys into chat.
Quick quiz
1. When do Amazon Q Developer IDE plugins end support?
30 April 2027.
2. What is a Kiro spec?
Structured requirements Kiro uses to plan, build and verify code.
3. Which sign-in options does Kiro offer?
GitHub, Google, AWS Builder ID, or IAM Identity Center.
4. Is Q Developer in the AWS Console affected?
No, it continues.
Save tokens and money
Specs cost tokens up front but save rework on big features. For small fixes, skip the spec and use chat. Keep steering files short and specific.