Amazon Q Developer Is Being Retired: What Kiro Means for AWS Developers
Cloud Platform EngineeringAWS will block new Amazon Q Developer signups on May 15, 2026, and end support for IDE plugins entirely by April 30, 2027 — replacing the product with Kiro, an agentic development environment AWS describes as “built from the ground up for spec-driven development.”
Context
Amazon Q Developer launched as AWS’s entry into the AI coding assistant market, competing directly with GitHub Copilot and Cursor through tight IDE integration and code generation capabilities. For many AWS-embedded teams, it became the default AI layer in VS Code and JetBrains workflows.
The retirement signals that AWS believes that approach is no longer sufficient. The company stated explicitly that “the most impactful AI developer experiences go far beyond code generation and completion” — requiring the kind of structured project understanding and agentic orchestration that a code completion plugin can’t deliver.
The Detail
The transition timeline is precise. New Q Developer Free Tier and subscription signups stop May 15, 2026. On May 29, Opus 4.6 is removed from Q Developer Pro. Full end-of-support for IDE plugins hits April 30, 2027. Existing subscribers retain access through that final date, and AWS has committed to critical bugfixes during the transition window. Q Developer’s integrations inside the AWS Management Console and first-party AWS service experiences are unaffected.
Kiro is the replacement, and its architecture is a departure from the assistant-first model. The core primitives are:
- Specifications: Structured natural-language requirements that drive implementation — the agent works from a spec, not a chat thread
- Hooks: Automated triggers on file save or commit events, enabling consistent enforcement at the workflow boundary
- Steering files: Project-level configuration encoding architecture context so the agent understands constraints before it writes a line
- Custom subagents: Domain-specific AI agents for specialized tasks
- Powers: Composable capability modules extending base functionality
The platform also includes inline chat, terminal integration, and MCP support — making it compatible with the growing ecosystem of MCP-aware tooling already deployed in AWS environments.
The Pattern
AWS has now retired or fundamentally repositioned every early-phase AI developer tool it shipped: Q Developer joins a pattern of first-generation products giving way to agentic successors. AWS Strands Agents followed the same trajectory — initial launch as a capability layer, then reengineered with agentic orchestration at the core. The spec-driven framing of Kiro mirrors how AWS is positioning its entire agentic stack: structured inputs, constrained outputs, observable pipelines.
The So What
Teams running Q Developer in production have 12 months to migrate, but the practical window is shorter. Developer tooling changes take longer in enterprise environments than vendors acknowledge — onboarding, security review, and workflow documentation don’t happen in the last 30 days. Engineering leads embedded in AWS should be evaluating Kiro now, not in Q4. The spec-driven model also requires a different workflow discipline from the team; that culture change starts before the migration, not after.
Photo by Al Nahian on Pexels
Source: AWS DevOps Blog
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →