Amazon Q Developer Hold

coding-agentsdeveloper-aienterpriseawsidecode-transformationsecurity-scancliagents

Overview

Amazon Q Developer is AWS's AI assistant for building, operating, and securing software on AWS. It spans IDE plugins, CLI workflows, console assistance, and guided transformations for Java and .NET modernization, with security scanning aligned to AWS deployment patterns (Amazon Q Developer).

The product is being split up. On 30 April 2026 AWS announced that the Amazon Q Developer IDE plugins (VS Code, JetBrains, Eclipse, Visual Studio) and paid subscriptions reach end of support on 30 April 2027, and it points customers to Kiro, its agentic IDE and CLI; the Q Developer CLI had already been rebranded as Kiro CLI in November 2025 (Kiro docs), and Java upgrades and .NET porting are offered through AWS Transform. Amazon Q Developer in the AWS Management Console, the AWS documentation and Slack or Microsoft Teams stays available (AWS DevOps Blog). For new IDE and CLI adoption the product is therefore a dead end.

Adoption Signals

  • AWS blocked new Amazon Q Developer Free Tier and subscription sign-ups from 15 May 2026, made newer coding models such as Opus 4.7 available only in Kiro, and set 30 April 2027 as end of support for the IDE plugins and paid subscriptions (AWS DevOps Blog).
  • The console, documentation, mobile app and chat-app (Slack, Microsoft Teams) experiences are explicitly excluded from the sunset (AWS DevOps Blog).
  • The Amazon Q Developer CLI has been rebranded to Kiro, and the Amazon Q Developer subscription console is now the Kiro console for administrators (Amazon Q Developer User Guide).
  • Kiro's migration guide carries VS Code settings over, but Kiro has no native plugins for Visual Studio or Eclipse, so users of those IDEs must switch editor or use the Kiro CLI (Kiro docs).
  • The .NET porting capability, previewed as Amazon Q Developer transformation capabilities for .NET porting, became generally available as the separate service AWS Transform for .NET on 15 May 2025 (AWS What's New).

Risks

  • Hard end-of-support date. After 30 April 2027 the IDE plugins and paid subscriptions are unsupported; plugins still installed after that date are an unpatched client with access to source code (AWS DevOps Blog).
  • Prompts may include account or resource metadata that must stay within approved logging and retention policies, both in the remaining console features and in whichever successor tool replaces the plugins.
  • IAM policies generated by Q and merged without review can grant overly broad permissions.
  • Forced migration. Estates standardised on the IDE plugins must move to Kiro or another assistant before the deadline, including re-approval of a new client, new data flows and new administration; Visual Studio and Eclipse users have no native Kiro plugin (Kiro docs).
  • Model lag until retirement. Newer coding models are reserved for Kiro, so teams that stay on the plugins until the last day work with an increasingly outdated assistant.

Pros & Cons

Advantages

  • Existing AWS estates already run it with IAM Identity Center and AWS Organizations administration, so current users keep working until the 30 April 2027 end of support.
  • The assistant in the AWS Management Console, AWS documentation, Console Mobile App and Slack or Microsoft Teams is excluded from the sunset and stays available.
  • There is a migration path inside the AWS tool chain: AWS documents that the inline suggestions, chat and code generation of the IDE plugins are available in Kiro.

Disadvantages

  • New Free Tier and paid sign-ups have been blocked since 15 May 2026, and the IDE plugins and paid subscriptions lose support on 30 April 2027.
  • Newer coding models such as Opus 4.7 are only offered in Kiro, so the Q Developer plugins fall behind on model quality until they are retired.
  • Migration is not a drop-in swap: Kiro has no native Visual Studio or Eclipse plugins, the transformation features moved to AWS Transform, and the new client needs its own security and data-handling review.

Recommendation

Hold Amazon Q Developer for new rollouts. New subscriptions are no longer possible, the IDE plugins and paid subscriptions lose support on 30 April 2027, and AWS itself points customers to Kiro. Existing users should plan the migration now rather than close to the deadline: evaluate Kiro if the team wants to stay in the AWS tool chain, or move to another assistant already on this radar, such as Claude Code, Cursor or GitHub Copilot (all Adopt). Either way, run a fresh security and data-handling review for the new client, and plan separately for Visual Studio and Eclipse users.

What remains supported can stay in use: Amazon Q Developer in the AWS Management Console, the AWS documentation, the Console Mobile App and Amazon Q Developer for chat apps in Slack and Microsoft Teams (AWS DevOps Blog). Keep IAM-scoped identities, logging review and mandatory human approval for infrastructure changes on those features. Run Java upgrades and .NET porting through AWS Transform on bounded services with golden tests before estate-wide campaigns.

Sources

Danışmanlık

Radardan uygulamaya

Teknolojileri değerlendirdiniz — bunları güvenli ve ölçülebilir şekilde üretim sistemlerine taşımanıza yardımcı oluyoruz.

Yapay Zeka Eğitimleri

Yapay Zeka Eğitimleri

Ekiplerinizi yapay zekaya hazırlıyoruz. Eğitimlerimiz soyut kavramları uygulanabilir yetkinliğe dönüştürür. Anlaşılır. Pratik. Uygulayanlar için.

Daha fazla bilgi edin