Amazon Q Developer
An AWS coding assistant offering inline suggestions, chat, and agentic tasks across IDEs and the console. AWS closed new IDE-plugin signups and subscriptions May 15, 2026 and IDE/subscription support ends April 30, 2027, pointing migrating users to Kiro; the AWS Console and other first-party AWS Q experiences are unaffected.
The verdict on Amazon Q Developer: Existing Q Developer subscribers on cloud-native, AWS-heavy projects who need suggestions aware of AWS APIs and services while planning a migration to Kiro Amazon Q Developer's real value was always narrow: developers building on AWS who needed an assistant that understood S3, Lambda, DynamoDB, and IAM without constant hand-holding. Pricing: IDE plugin & paid subscription retiring: new signups closed May 15, 2026, support ends Apr 30, 2027 (existing subscribers may add seats), migrate to Kiro; AWS Console and first-party AWS Q experiences unaffected.
Best For
Existing Q Developer subscribers on cloud-native, AWS-heavy projects who need suggestions aware of AWS APIs and services while planning a migration to Kiro
Standout Feature
Deep awareness of S3, Lambda, DynamoDB, and IAM specifics that general coding assistants don't have
TL;DR
Genuinely useful for AWS-heavy projects, being retired with support ending April 2027, so plan a migration to Kiro.
Alternatives
Overview
Not yet reviewedProduct quality is assessed from original evidence. How reviews work.
Amazon Q Developer (formerly CodeWhisperer) is AWS's AI coding assistant, built specifically around the AWS ecosystem and designed for developers building cloud-native applications on AWS infrastructure. Its primary differentiator is deep awareness of AWS APIs, SDKs, and service integrations: suggestions for S3 operations, Lambda functions, DynamoDB queries, and IAM policies are noticeably more accurate and idiomatic than general-purpose coding tools that generate AWS code from generic training data. Q Developer includes a security scanning feature that checks code for common vulnerabilities, SQL injection, path traversal, cross-site scripting, using Amazon's own security tooling.
AWS closed new Q Developer IDE plugin signups and subscriptions on May 15, 2026, with IDE plugin and paid subscription support ending April 30, 2027; existing subscribers can still add seats during that window. AWS's own Management Console and other first-party AWS Q experiences are unaffected by this wind-down. Q Developer integrates with VS Code, JetBrains, and the AWS console directly.
For teams already using it on AWS-heavy projects, it adds AWS-specific accuracy, but new adopters should look at Kiro, the tool AWS points migrating users toward, rather than signing up for the IDE plugin fresh.
The source of the legacy catalog rating and review count has not been substantiated. Neither is presented here as a verified review rating or included in review structured data.
Workflow Fit Scores are separate, use-case-specific editorial judgments, not user-review averages. Read the Fit Score methodology.
- • Best for AWS-heavy projects
- • Built-in security scanner
- • Free for individual use
- • Tracks open-source references
- • Less impressive outside AWS ecosystem
- • Not as capable as Cursor for complex tasks
- • JetBrains support is limited
Key Features
- Code generation
- Security vulnerability scanning
- AWS service integration
- IDE plugins
- Reference tracking
Trust & Data
Verified 2026-09
- Training on your data
- Opt-out availableThe Pro tier explicitly does not use customer content for service improvement or model training; the Free tier may use content (questions, responses, generated code) for training, with opt-out available via AWS Organizations policy or per-IDE settings.
- Compliance
- Not published
- Retention
- Not published
- Export
- Not published
Source: aws.amazon.com
As published by the vendor. Verify independently before purchase decisions.
Our Take
That specificity mattered. The problem now is that AWS closed new signups in May 2026 and support ends April 2027, with migration to Kiro as the stated path. If you're currently using it on AWS-heavy projects, start planning that migration now rather than waiting. For anyone evaluating it fresh, there's no practical reason to start with a tool on a retirement schedule.