Amazon Q Developer helps with software development and AWS-related work.
Amazon Q Developer
Explore features, practical uses and pricing below.
Amazon Q Developer provides coding assistance and help with AWS applications and resources. Developers can ask questions about code, receive suggestions while editing, request changes and investigate code issues. In AWS surfaces, it can explain architecture and account resources. It suits developers working with AWS who want assistance close to their repository or cloud environment, while also supporting development tasks outside AWS.
The IDE chat documentation describes code explanations, debugging, refactoring and test generation. With agentic coding enabled, Q can update files directly and present a diff that the developer can inspect or undo. It can also suggest shell commands and run commands it considers low risk. This makes the interaction an active development workflow rather than a conversation that only returns snippets.
Context controls allow the developer to include files and folders explicitly. Supplying the relevant module and its tests helps focus a request on the actual project. Separate chat conversations do not retain each other's context, so a new task may need its own explanation of requirements and boundaries.
Q's code review workflow can examine a file, changes or a repository in supported IDEs. Findings can be opened at the affected code, explained and used to request a remediation. The review scope depends on the prompt and available changes, so specify whether you want the diff or the complete file assessed. Automatic reviews while typing have a separate Pro subscription requirement.
For AWS work, resource questions let users investigate account infrastructure through natural-language prompts. This can support understanding an environment before changing application configuration. Access to resource information depends on the user's AWS permissions; installing an editor extension does not grant administrative access to an account.
For an API handler that returns an incorrect validation error, provide the failing request, handler and relevant tests. Ask Q to explain the current path before proposing a patch. Review the diff, run the test that demonstrates the failure and request a review of the changed code. If the behavior also depends on an AWS resource, check the relevant configuration separately under an appropriately scoped identity. Keep the implementation decision and any cloud action under the developer's control.
AWS has announced that support for Amazon Q Developer IDE plugins ends on April 30, 2027, and points users toward Kiro for similar editor capabilities. This notice concerns the IDE plugins; it should not be generalized into a claim that every Q Developer surface has the same end date. Consider the migration work before adopting an editor workflow for the long term.
Generated patches and remediation suggestions can be incorrect or incomplete. Verify language and IDE support for the specific capability, and treat an empty review result as limited feedback rather than assurance that the application is secure.
The official pricing page separates Free and Pro tiers, with different request limits, transformation allowances and administration features. The getting-started guide describes Builder ID access for editor use and permission requirements for AWS surfaces. Check the intended sign-in method and current plan table: organization controls and account-level allowances are not identical to an individual's access. AWS resources used by an application have their own service costs.