Amazon Q Developer (formerly CodeWhisperer)

AWS-native AI assistant with security scans, AWS code suggestions, and reference tracking.

AI Coding ToolsIntermediate

Why

Stack Overflow's 2024 survey found 62% of developers currently use AI tools (up from 44% in 2023), with 82% of them using AI to write code. Amazon Q Developer is tuned for AWS APIs (CDK, SDK, IAM) and includes reference tracking (it flags when a suggestion resembles open-source code) and security scanning.

For AWS-heavy teams it reduces boilerplate and surfaces IAM/permission mistakes early.

When

Use Q Developer when you build on AWS heavily, need reference-attribution compliance, or want inline security scans. General-purpose tools are better for non-AWS work.

How

1. Install the AWS Toolkit extension and connect with Builder ID or IAM Identity Center. 2. Completions: Tab to accept; suggestions favor AWS SDK patterns. 3. /dev (agent) in VS Code: multi-file feature development with a plan you approve. 4. /security: scans the file/repo for findings with remediation suggestions. 5. /doc: generates docs from code. /test: generates tests. 6. Reference tracking logs when a suggestion matches open-source code.

Example

In a CDK stack file, type "add an S3 bucket with" — Q suggests: const bucket = new s3.Bucket(this, "Data", { encryption: s3.BucketEncryption.KMS, enforceSSL: true, blockPublicAccess: s3.BlockPublicAccess.BLOCK_ALL, }); Run /security to flag any bucket without enforceSSL across the repo.

Common Problems

⚠Error: Cannot find module 'xxx' → run `npm install xxx` and restart the editor/extension host.
⚠Error: "Extension not activated" / greyed-out AI features → check the API key setting and network; run the extension's "Check Connection" command.
⚠Error: Rate limit 429 → upgrade plan or reduce request frequency; check the tool's usage dashboard for quota.

Best Practices

✓Run /security in CI on AWS infra code to catch misconfigurations early.
✓Use /dev for multi-file AWS features; it plans before editing.
✓Measure the outcome with a concrete metric (time saved, defect rate, test coverage) so the practice can be justified and improved.

FAQ

What is Amazon Q Developer (formerly CodeWhisperer)?

AWS-native AI assistant with security scans, AWS code suggestions, and reference tracking. It helps developers quickly grasp the core value and use cases of Amazon Q Developer (formerly CodeWhisperer).

How do I get started with Amazon Q Developer (formerly CodeWhisperer)?

To get started with Amazon Q Developer (formerly CodeWhisperer), focus on these points first: Install the AWS Toolkit extension and connect with Builder ID or IAM Identity Center.

What are common mistakes with Amazon Q Developer (formerly CodeWhisperer)?

Common mistakes when using Amazon Q Developer (formerly CodeWhisperer) include: Error: Cannot find module 'xxx' → run `npm install xxx` and restart the editor/extension host.; Error: "Extension not activated" / greyed-out AI features → check the API key setting and network; run the extension's "Check Connection" command.; Error: Rate limit 429 → upgrade plan or reduce request frequency; check the tool's usage dashboard for quota..

What are the best practices for Amazon Q Developer (formerly CodeWhisperer)?

Best practices for Amazon Q Developer (formerly CodeWhisperer) include: Run /security in CI on AWS infra code to catch misconfigurations early.; Use /dev for multi-file AWS features; it plans before editing.; Measure the outcome with a concrete metric (time saved, defect rate, test coverage) so the practice can be justified and improved..

How do I learn more about Amazon Q Developer (formerly CodeWhisperer)?

Start with the official docs, then search real-world examples on GitHub. Validate patterns in a small scratch repo before applying them to production code.