Amazon Q Developer
Amazon Q Developer is AWS's AI coding assistant and the successor to CodeWhisperer. It offers inline suggestions, agentic multi-step tasks, and deep AWS context.
Last reviewed: June 2026
Feature names and pricing tiers change. Confirm current plans at Amazon Q Developer pricing and AWS documentation.
Where Q Developer Runs
| Surface | Best for |
|---|---|
| VS Code extension (AWS Toolkit) | Daily web and cloud development |
| JetBrains IDEs | Java, Kotlin, Python teams on IntelliJ family |
| Visual Studio / Eclipse (preview) | .NET and legacy IDE shops |
| CLI / terminal | Natural-language bash, quick commands |
| AWS Console chat | Account questions, architecture, troubleshooting |
Install: Amazon Q Developer in your IDE. Free tier available with AWS Builder ID (no AWS account required for basic IDE use).
Feature Overview
| Feature | What it does |
|---|---|
| Inline completions | Multiline suggestions from comments and surrounding code |
| Chat | Explain, debug, and refactor in sidebar |
| Agentic coding | Multi-step plans to implement features, tests, and refactors across files |
@workspace | Project-wide context for auth flows, dependencies, and architecture questions |
| Security scan | Vulnerability detection with suggested fixes |
| Code transformations | Framework/version upgrades (e.g. Java 8 → 17) |
Agentic tasks need the same verification checklist as Cursor or Codex agents.
Agentic Workflow
- Open the Amazon Q panel in your IDE
- Describe the feature with scope: files, constraints, test command
- Review Q's step-by-step plan before approving execution
- Inspect diffs file by file; run tests locally
Example prompt:
Add input validation to the Lambda handler in src/handlers/orders.ts.
Use existing error types from src/errors.ts.
Generate unit tests. Do not change IAM or CloudFormation files.
Docs: Agentic coding experience.
AWS-Aware Strengths
Q Developer is built on Amazon Bedrock and augmented with AWS knowledge:
- Generate AWS CLI commands and explain console errors
- Answer questions about your account resources (with appropriate IAM)
- Suggest patterns aligned with AWS best practices
If your team lives in Lambda, CDK, Terraform on AWS, and IAM, Q reduces context-switching to external docs. For multi-cloud or non-AWS stacks, compare Cursor, Codex, or Gemini Code Assist.
For product features powered by models (your app's chat UI), use LLM APIs or AI Platforms (Bedrock). The IDE plugin alone is not enough.
Amazon Q vs Other Tools
| Need | Best fit |
|---|---|
| AWS-native development | Amazon Q Developer |
| OpenAI / ChatGPT stack | OpenAI Codex |
| GCP / Android | Gemini Code Assist |
| AI-first IDE | Cursor or Devin Desktop |
| GitHub-centric enterprise | GitHub Copilot Enterprise |
| Terminal automation | Claude Code or Codex CLI |
Pricing Snapshot
Typical tiers (confirm on AWS):
- Free: Builder ID; limited agent and chat usage
- Pro: per-user subscription for expanded agentic features
- Enterprise: IAM Identity Center, admin controls, policy
See Cost, Latency, and Tokens when estimating agent-heavy usage.
For Teams
| Question | Where to look |
|---|---|
| Data handling / training | AWS Q Developer privacy and Bedrock policies |
| SSO / enterprise | IAM Identity Center + Pro/Enterprise |
| Approved tools list | Team AI Policy |
| Regulated workloads | Legal review before sending code to cloud models |
Add Q Developer to your Choosing a Tool procurement matrix alongside Copilot Enterprise and Cursor Business.