IA
AWS has just confirmed the end of one of its flagship developer tools. If your teams use Amazon Q Developer, you now have a deadline to put on the calendar, and a migration to plan toward its successor: Kiro.
No need to panic, but a decision to make. Here’s exactly what’s happening, what’s affected, what isn’t, and the business takeaway.
Amazon Q Developer is AWS’s AI coding assistant, their answer to tools like GitHub Copilot or Cursor. Concretely, it helps developers write, fix, and understand code, either in their editor via plugins, or through a paid subscription (the Pro version at 19 dollars per user per month).
Many teams adopted it precisely because it integrates natively with the AWS ecosystem. That’s exactly what makes the announcement significant.
New signups are already closed. As of May 15, 2026, you can no longer sign up for paid Q Developer. Existing subscriptions can still add users, but the door is closed to newcomers.
End of support is scheduled for April 30, 2027. Amazon Q Developer’s IDE plugins and paid subscriptions will stop being maintained on that date. That leaves about twelve months to migrate. “End of support” means that after that day, there are no more updates, no more bug fixes, no more assistance.
The best models are already reserved for the successor. As of May 29, 2026, the Opus 4.6 model is no longer available on Q Developer Pro. Existing models like Opus 4.5 remain accessible, but the latest coding models, including Opus 4.7, are available exclusively on Kiro. It’s a classic migration lever: if you want the most capable tool, you have to switch.
This is the point many articles miss, and the one that avoids needless panic. What’s disappearing is the IDE plugins and the paid subscriptions. Not Q Developer everywhere.
Amazon Q Developer in the AWS console and the first-party AWS experiences (documentation, mobile app, Slack, Microsoft Teams) are not affected. In other words, the assistant built into your console continues to exist. Only the “in the code editor” version your developers use is reaching end of life.
Kiro is AWS’s new AI development environment, launched in mid-2025. Built on VS Code and powered by Claude via Amazon Bedrock, it doesn’t just suggest code: it’s an “agentic” tool, capable of executing tasks more autonomously.
Its defining feature is spec-driven development. Instead of going straight from prompt to code, Kiro first generates a requirements document, a technical design document, and a structured task list. Code is only written once that plan is validated. AWS’s intent is clear: to fight “vibe coding,” that habit of asking an AI to generate code and accepting it without any framework, which produces undocumented software that’s hard to maintain.
On pricing, Kiro offers a limited free tier and a Pro plan at roughly 19 to 20 dollars a month, comparable to Cursor or Q Developer. Nothing dramatic on price, then, but a different tool philosophy.
Here’s the read for decision-makers.
If your teams use Q Developer in their editors. You have a migration to plan before April 2027. It’s not an overnight emergency, but migrating the coding tool of an entire team isn’t something you improvise: you have to train, adjust workflows, test, and support a change of habits. Twelve months go by fast when you have a product roadmap to hit in parallel.
If you were considering adopting Q Developer. Too late, signups are closed. Look directly at Kiro, or compare with market alternatives (Cursor, Copilot) before committing.
The shift in philosophy matters as much as the tool. Moving from Q Developer to Kiro isn’t just changing software. Kiro imposes a more structured, more disciplined approach. For some teams, that’s a gain in quality and maintainability. For others, used to the speed of prompt-to-code, it’s a learning curve to absorb. This human dimension is often underestimated in tool migrations.
This announcement isn’t isolated. It fits a broader strategy where AWS is consolidating its AI coding offering around a single, modern, agentic tool, rather than maintaining several products in parallel. It’s the same logic that gave rise to AWS’s MCP Server: making the platform the prime playground for AI agents, under control and with governance.
For a company running on AWS, the message is clear. The ecosystem moves fast, tools are regularly replaced, and every transition demands anticipation. That’s not a problem in itself: it’s the normal rhythm of modern cloud. The real question is who, in your organization, watches these deadlines and plans migrations before they become urgent.
That’s precisely the kind of monitoring a dedicated AWS team builds into its daily work: anticipating end-of-support dates, preparing migrations, and making sure your developers never wake up one morning to a tool that no longer gets updates.
Amazon Q Developer (IDE plugins and paid subscriptions) is shutting down in April 2027, in favor of Kiro, AWS’s agentic IDE. Signups have already been closed since May 2026, and the best models are reserved for the successor. The AWS console and first-party integrations are not affected.
For decision-makers, this is less bad news than a reminder: on AWS, tools evolve, and anticipating migrations is part of the job. Better to plan this transition calmly over twelve months than to face it in a rush.
A project, an infra drifting, a bill spiraling. Tell us what's blocking you in Miami, we'll come back with a plan.
