Amazon Q Developer Announces End-of-Support Timeline
According to an AWS blog post, Amazon Q Developer IDE plugins and paid subscriptions will reach end of support on April 30, 2027, providing a 12-month transition window. The post introduces a new agentic development environment called Kiro and describes it as built for spec-driven development, with features such as structured "Specs", automated "Hooks", project-level "Steering files", custom subagents, and composable "Powers". The blog also says new Q Developer signups will be blocked starting May 15, 2026, and that model availability will change on May 29, 2026, when Opus 4.6 will be removed from Q Developer Pro while Opus 4.5 and other existing models remain available; the post references newer coding models including Opus 4.7. The announcement advises customers to transition to Kiro over the coming year.
What happened
According to an AWS blog post, Amazon Q Developer IDE plugins and paid subscriptions will reach end of support on April 30, 2027, giving customers a 12-month transition window. The same post states that new Q Developer signups will be blocked starting May 15, 2026, and that model availability will change on May 29, 2026, when Opus 4.6 will no longer be available on Q Developer Pro while Opus 4.5 and other existing models will remain available. The blog post also introduces Kiro, described as an agentic development environment built for spec-driven development.
Technical details
Per the AWS blog post, Kiro is presented as an IDE and CLI environment that operates from structured specifications rather than individual prompts. The announcement lists key capabilities attributed to the blog post:
- •Specs: structured, natural-language requirements that drive end-to-end implementation.
- •Hooks: automated triggers on file save, commit, or other events to run tests or enforce standards.
- •Steering files: project-level configuration carrying persistent context about architecture and constraints.
- •Custom subagents: domain-specific agents for tasks such as security review or API contract validation.
- •Powers: composable modules that extend agentic behavior for specific workflows.
The post says Kiro retains Q Developer features such as agentic coding, inline chat, terminal integration, and MCP support.
Industry context
Editorial analysis
Vendor transitions from embedded IDE assistants to purpose-built agentic environments reflect a broader industry shift toward tooling that maintains persistent project context, enforces CI/CD integration, and encodes architecture-level constraints. Companies introducing agentic IDEs commonly emphasize structured specs, event hooks, and pluggable subagents to reduce prompt fragility and improve reproducibility.
What to watch
For practitioners
monitor the migration tooling and documentation AWS publishes for moving projects from Q Developer to Kiro, parity of coding-model behavior (notably the removal of Opus 4.6 and references to Opus 4.7), and any changes to pricing or integration points for IDEs and CI systems. Adoption signals to follow include IDE plugin updates for VS Code and JetBrains, and guidance on converting existing Q Developer steering/context into Kiro specs.
Key Points
- 1AWS sets a 12-month end-of-support window for Q Developer, creating a clear timeframe for migration planning and testing.
- 2The introduction of Kiro emphasizes spec-driven, agentic workflows, matching an industry trend toward persistent project context and composable agents.
- 3Model lifecycle changes, including removal of Opus 4.6, highlight the operational impact of vendor model deprecations on developer tooling and CI integration.
Scoring Rationale
A 12-month end-of-support timeline for a widely used IDE assistant, paired with migration to the new Kiro agentic environment, has direct operational impact on developer teams' tooling and CI plans. Replacing the page's generic product-page source with the official announcement strengthens authority; it remains a solid product-lifecycle event.
Sources
Public references used for this report.
Practice with real Retail & eCommerce data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Retail & eCommerce problems
