Amazon Q Developer End-of-Support Announcement

Why It Matters

The shift forces developers to adopt a more holistic AI‑assisted workflow, positioning Amazon’s Kiro as the next‑generation tool for enterprise software delivery. It also consolidates Amazon’s AI model offerings, driving adoption of its latest Opus 4.7 capabilities.

Key Takeaways

• Q Developer IDE plugins end support April 30, 2027.
• New Q Developer signups stop May 15, 2026.
• Opus 4.6 removed; Opus 4.7 exclusive to Kiro.
• Kiro provides spec‑driven, agentic IDE and CLI for whole projects.
• Migration guide and plugins help customers transition smoothly.

Pulse Analysis

Amazon is winding down its Q Developer IDE plugins, with full support ending on April 30, 2027. The move follows a year of learning that developers want AI that sees beyond line‑by‑line suggestions and can reason about an entire codebase. By halting new sign‑ups on May 15, 2026 and retiring the Opus 4.6 model, Amazon is nudging customers toward its next‑generation platform, Kiro. The transition window gives existing subscribers a year to evaluate the new tool while Amazon continues to push critical bug fixes to the legacy plugins.

Kiro is marketed as an agentic development environment built from the ground up for spec‑driven workflows. Users write structured natural‑language specifications that drive automated planning, implementation, and verification across the whole repository. Features such as Hooks automate testing or documentation on file saves, while Steering files preserve architectural context for consistent output. Custom sub‑agents let teams embed domain‑specific intelligence—security scans, API contract checks, or infrastructure provisioning—directly into the coding loop. By bundling the familiar inline chat, terminal integration, and MCP support from Q Developer, Kiro aims to become a one‑stop AI‑augmented IDE.

For enterprises, the shift signals a deeper commitment by Amazon to embed generative AI into the software development lifecycle. The exclusive availability of the latest Opus 4.7 model on Kiro creates a clear incentive to migrate, especially for organizations that rely on cutting‑edge code generation and automated compliance. The migration guide and continued plugin listings reduce friction, but teams must allocate resources to rewrite specifications and train custom sub‑agents. In the broader market, Kiro’s spec‑driven approach could set a new benchmark, pushing competitors to offer similarly holistic, context‑aware AI development tools.