Amazon Q Developer Review (2026): AWS's AI Coding Assistant in Transition

Amazon Q Developer Review (2026): AWS's AI Coding Assistant in Transition

Amazon Q Developer is AWS's AI coding assistant, the tool that grew out of the service formerly known as Amazon CodeWhisperer. It works as an in-IDE assistant and a command-line companion, layering inline code completion, a chat interface, and multi-step agents on top of deep AWS account and service integration. This hand-reviewed update covers what the product is, current pricing, its genuine strengths inside the AWS ecosystem, and one fact that reshapes any 2026 buying decision: AWS has announced an end-of-support timeline and is steering customers toward its successor, Kiro.

What is Amazon Q Developer?

Amazon Q Developer began life as CodeWhisperer, a straightforward code-completion tool, and was rebranded and expanded into Amazon Q Developer as AWS folded generative-AI assistance across its developer stack. In its mature form it offers several surfaces:

• IDE plugins for Visual Studio Code, JetBrains IDEs, Visual Studio, and Eclipse, providing inline completions and an in-editor chat panel.
• A CLI experience that adds AI-assisted autocompletion and chat directly in the terminal, locally and over SSH.
• Agents that take on multi-step work: implementing a feature, generating unit tests, reviewing code, and performing large-scale code transformation such as upgrading legacy Java 8 or 11 projects to Java 17 or 21, handling dependency and syntax changes along the way.
• AWS-native chat that can answer account-level questions ("list my Lambda functions"), reason about your resources, and generate AWS CLI commands and Infrastructure-as-Code.

The defining trait is context. Where most assistants only see your open files, Amazon Q Developer can also see your AWS environment, which makes it unusually good at tasks that touch cloud services, IAM, and AWS-specific APIs.

Important: end-of-support timeline

Any honest 2026 review has to lead with this. In April 2026 AWS published an end-of-support announcement for the Amazon Q Developer IDE plugins and paid subscriptions. New sign-ups closed on May 15, 2026, and end of support is scheduled for April 30, 2027, giving existing customers roughly a twelve-month transition window. AWS is directing developers to Kiro, a new agentic, spec-driven development environment, where the newest coding models are now offered exclusively. Existing Q Developer Pro or Kiro subscribers keep access to the Q Developer IDE plugins, with critical bug fixes, through April 30, 2027.

In practical terms: if you are not already using Amazon Q Developer, you generally cannot start a fresh paid subscription, and the product is on a defined path to retirement. The details below describe the tool as it stands during this transition.

At a glance

Pricing

Amazon Q Developer has kept a simple two-tier structure in USD.

The Free tier requires only an AWS Builder ID and includes code completions, an allotment of roughly 50 agentic requests per month spanning chat, code transformation, and vulnerability scanning, plus a capped amount of Java code transformation. It is enough to evaluate the tool and cover light individual use.

Amazon Q Developer Pro is $19 per user per month. It raises the limits across agentic requests, code transformation, and scanning, and adds the features teams care about: administrative controls, organizational user management through AWS IAM Identity Center, higher throughput, and intellectual-property indemnification, meaning AWS commits to defend customers against certain claims that generated code infringes third-party rights. Because sign-ups are closed to new customers, in practice these plans now apply mainly to organizations already on the product.

Key features

• Inline completions and chat across four major IDE families, covering the day-to-day autocomplete and "explain this" workflows most developers expect.
• Agentic development that plans and executes multi-file changes, then explains what it did, rather than only suggesting the next line.
• Code transformation at scale, most notably automated Java version upgrades that manage dependencies and refactor syntax, aimed at reducing tedious modernization work.
• Automated code review and test generation, producing unit tests and flagging issues as part of a review pass.
• Security scanning that detects common vulnerabilities and suggests remediations.
• Deep AWS integration, the headline differentiator: account-aware answers, resource inspection, and generation of AWS CLI commands and IaC (CloudFormation, CDK) grounded in your actual environment.

Strengths and limits

The strengths cluster tightly around AWS. If your work lives in Lambda, ECS, DynamoDB, IAM, and CloudFormation, Amazon Q Developer understands that world in a way general-purpose assistants do not. It can answer questions about your own resources, scaffold service integrations with the right APIs, and translate an intent into AWS-native commands. The code-transformation agents address a real and painful problem, and the Pro tier's IP indemnity and IAM-based administration are meaningful for risk-conscious enterprises.

The limits are equally clear. Outside AWS, the tool is a competent but not category-leading coding assistant; its inline suggestions and general agentic quality are frequently rated behind the strongest rivals. Its advantages shrink for teams on other clouds or with cloud-agnostic codebases. And the transition context is itself a limit: with new signups closed and support ending in April 2027, adopting Amazon Q Developer today means committing to a product with a known sunset date and a migration ahead. Evaluating Kiro, GitHub Copilot, or Cursor is the sensible parallel step.

Pros and cons

Pros

• Deepest AWS-account and AWS-service awareness of any mainstream coding assistant
• Practical code-transformation agents, especially automated Java upgrades
• Broad IDE coverage (VS Code, JetBrains, Visual Studio, Eclipse) plus a CLI
• Usable free tier and a flat $19/user/month Pro tier
• Pro includes IP indemnification and IAM-based admin controls

Cons

• End of support announced; new signups closed, EOS April 30, 2027
• AWS steers customers to Kiro, where the newest models now live
• General coding quality often rated behind Cursor, Copilot, and Claude Code
• Value drops sharply outside the AWS ecosystem
• Adopting now means planning a migration, not a long-term bet

How it compares

GitHub Copilot is the broadest and most accessible rival, with individual Pro at $10/month, Business at $19/user/month, and Enterprise at $39, alongside a free tier. It has the largest community and the widest IDE reach, and in mid-2026 it moved premium and agentic usage onto a usage-based AI-credits model while keeping code completions unlimited. For teams that are not AWS-centric, Copilot is usually the more future-proof default. Our Amazon Q Developer vs GitHub Copilot comparison breaks down the trade-offs in detail.

Cursor takes a different shape: an AI-first IDE (around $20/month) built for fast tab-completion and multi-agent editing. It is a fuller editor-replacement experience and a favorite for developers who want AI woven through the whole editing loop, but it has no special AWS awareness.

Claude Code, Anthropic's terminal-native agent, sits at the autonomous end, strong at long-running, multi-file tasks and refactors driven by frontier models. It, too, is cloud-agnostic. Against all three, Amazon Q Developer's distinguishing card is AWS context rather than raw coding horsepower, and that card is precisely what Kiro is meant to carry forward.

Who it's for

Amazon Q Developer makes the most sense for AWS-heavy teams that already have it deployed: organizations building primarily on AWS services, running large Java estates that benefit from transformation agents, and valuing the IAM-based governance and IP indemnity of the Pro tier. For those teams, the account-aware chat and CLI generation genuinely speed up cloud work.

For everyone else, and for anyone starting fresh in 2026, the calculus has changed. With new subscriptions closed and support ending in April 2027, new adopters should evaluate Kiro as the AWS-endorsed successor, or choose a cloud-agnostic tool such as GitHub Copilot or Cursor. Teams outside the AWS ecosystem gain little from Q Developer's core advantage and are better served elsewhere.

Verdict

Amazon Q Developer is a capable, AWS-specialized coding assistant whose real edge was never raw code quality but its unmatched understanding of the AWS environment: your resources, your services, your IaC. For AWS-native teams already using it, it remains useful through the transition window. But the defining fact of an August 2026 review is that AWS has put the product on a path to retirement, closing new signups in May 2026 and ending support on April 30, 2027, while pointing customers to Kiro. That makes it hard to recommend as a new adoption. Existing AWS teams should plan their migration; new evaluators should look at Kiro, GitHub Copilot, or Cursor first, and treat Amazon Q Developer as context for that decision rather than the destination.

FAQ

Is Amazon Q Developer free? There is a free tier, available with an AWS Builder ID, that includes code completions and roughly 50 agentic requests per month. The paid Amazon Q Developer Pro tier is $19 per user per month, though new signups are now closed.

What was Amazon Q Developer called before? It was formerly Amazon CodeWhisperer, which AWS rebranded and expanded into Amazon Q Developer.

Is Amazon Q Developer being discontinued? AWS announced end of support for the Q Developer IDE plugins and paid subscriptions: new signups closed May 15, 2026, and support ends April 30, 2027. AWS is directing developers to its successor, Kiro.

What makes it different from GitHub Copilot? Its deep AWS integration: it is aware of your AWS account and resources and can generate AWS CLI commands and IaC. Copilot is broader and cloud-agnostic. See our Amazon Q Developer vs GitHub Copilot comparison.

Should AWS teams still use it? Existing AWS teams can keep using it through April 30, 2027, but should plan a migration to Kiro or another assistant. New teams should evaluate Kiro, GitHub Copilot, or Cursor instead.