The rename, and why it still causes confusion
Two years on, this remains the most practical obstacle to using it. Search results, tutorials, Stack Overflow answers and internal documentation still say CodeWhisperer, while the console, the billing page and current AWS documentation say Q Developer.
Worse, “Amazon Q” covers several products — Q Developer, Q Business, and Q inside various AWS services — so a search for “Amazon Q” returns material about a different tool entirely.
When following a guide, check its date. Anything from before mid-2024 describes the older, narrower product, and the feature set has changed substantially since.
Account awareness, which nothing else offers
Connected to your AWS account, it answers questions about your actual infrastructure rather than about AWS in the abstract.
Which instances are running and what are they costing. Why a particular Lambda is failing. What this security group actually permits. Which resources are in a region you forgot about. These are questions people currently answer by clicking through the console for twenty minutes, and getting them answered in the editor or the console is the tool’s clearest value.
It needs IAM permissions to see those resources, which means an administrator has to enable it. An individual developer usually cannot switch this on alone, and that is the most common reason people evaluate Q Developer without ever seeing the feature that justifies it.
Code transformation, and what it realistically achieves
Automated upgrades of Java and .NET applications across language versions, run as a job over a whole codebase rather than file by file.
This addresses a real, expensive and deeply unglamorous problem: organisations sitting on unsupported runtimes, where the upgrade is mechanical, enormous, and impossible to justify against feature work.
It is not magic and should not be sold internally as such. It handles the mechanical majority — API changes, deprecated calls, syntax updates — and leaves the parts requiring judgement. Expect a substantial reduction in effort rather than an unattended migration, and expect a human to review and test the result properly.
For a large legacy estate that is still transformative arithmetic. It is the single feature most likely to justify the product on its own.
Security scanning in the loop
Vulnerability scanning is integrated into the assistant, flagging insecure patterns as they are written rather than in a separate pass weeks later.
Catching a problem at the point of writing is worth considerably more than catching it in a report, because the context is still in the developer’s head. This is a genuine advantage over tools that treat security as someone else’s stage.
General coding ability, honestly assessed
Outside AWS-specific work, Q Developer is competent and unremarkable. For ordinary application code, Cursor, Claude Code and Copilot generally produce better results.
That is not a criticism so much as a positioning statement. Nobody should choose Q Developer for its completions; they should choose it because their infrastructure is AWS and the account-aware answers, the transformation jobs and the AWS-native billing are worth more than a better autocomplete.
Many AWS teams run it alongside another assistant for exactly this reason, and that is a sensible arrangement rather than an admission of failure.
What you need to switch it on
- A supported editor — VS Code, JetBrains IDEs, Visual Studio — or the AWS Console and CLI.
- An AWS account. A free tier with monthly limits; a professional tier per user per month, billed through AWS.
- For account-aware features, IAM permissions configured by an administrator.
- An internet connection.
Processing, and the procurement advantage
Code is sent to AWS for processing. For organisations already running their infrastructure on AWS, that is frequently an easier conversation than adding a new vendor — the data processing agreement exists, the security review was done, and procurement has an existing relationship.
That procurement advantage is underrated and is a legitimate reason to prefer it. It is not a technical argument, and it decides plenty of real adoptions.
Which teams this is aimed at
Teams whose infrastructure is AWS, particularly those writing infrastructure-as-code or working across many services, where the account-aware answers save a constant tax.
Enterprises with Java or .NET applications on unsupported runtimes — the transformation feature addresses a problem few other tools touch.
Organisations already committed to AWS procurement, where adding a service beats approving a new vendor.
For teams on other clouds, or not on a cloud at all, there is little reason to choose it over a stronger general assistant.
The case for it on an AWS estate
- Answers about your real account, including cost questions — unique among these tools.
- Automated legacy upgrades for Java and .NET at codebase scale.
- Security scanning in the same tool, at the point of writing.
- AWS-native billing and IAM, removing a procurement conversation.
- A usable free tier for individual work.
What to expect
- General coding ability is mid-field. Not the reason to adopt it.
- Deep AWS coupling — little benefit on Azure, Google Cloud or on-premises.
- The rename confuses documentation, and much published material is stale.
- Account features need IAM setup, so individuals often cannot evaluate them.
- Transformation is not unattended — it reduces work rather than eliminating it.
Uninstalling it
Uninstall the extensions; nothing in your code depends on it. Any transformation jobs already run produced ordinary code in your repository.
What does not travel is the account-aware knowledge, which was never portable — it was answers about your infrastructure, not an asset you accumulated.
Where a general assistant serves better
- GitHub Copilot — stronger general assistance, no AWS account awareness.
- Cursor IDE — better day-to-day coding, cloud-agnostic.
- Tabnine — when self-hosting and licence provenance matter more.
- Sourcegraph Cody — enterprise-oriented, strong on large-codebase context.
Compiled from AWS documentation and public sources. The product was renamed from CodeWhisperer in 2024 and continues to change — verify current capabilities directly. We have not hands-on tested this tool. Last reviewed 16 August 2026.
