Amazon Q Developer
Sunset TransitionAmazon Q Developer is in transition: new signups are closed, IDE plugins and paid subscriptions sunset on 2027-04-30, while selected AWS first-party experiences continue.
About Amazon Q Developer
Amazon Q Developer remains available to existing customers during a transition period, but AWS closed new Q Developer account and subscription signups on 2026-05-15. The IDE plugins and paid Q Developer subscriptions are scheduled to reach end of support on 2027-04-30.
AWS recommends Kiro for the forward-looking developer workflow, while some Q Developer capabilities in the AWS Management Console and other first-party AWS experiences are not part of this IDE and subscription sunset.
For AI Toolset's decision workflow, new buyers should treat Amazon Q Developer as a migration and continuity question rather than a fresh greenfield purchase. Existing customers should review Kiro migration timing, remaining transformation work, and which AWS first-party Q experiences they still rely on.
Key Features
- ✓Transition status: New Q Developer account and subscription signups closed on 2026-05-15, and IDE plugins plus paid subscriptions are scheduled to reach end of support on 2027-04-30.
- ✓Existing-customer continuity: Existing subscribers can continue using supported Q Developer experiences during the transition window and may add users to active subscriptions under AWS's transition rules.
- ✓Kiro migration path: AWS recommends Kiro for forward-looking developer workflows, including agentic coding, inline chat, terminal integration, MCP, specs, hooks, steering files, custom subagents, and powers.
- ✓AWS first-party experiences continue: Q Developer in the AWS Management Console and selected first-party AWS surfaces are not part of the announced IDE-plugin and paid-subscription sunset.
- ✓Code transformation transition: Java upgrades and .NET porting delivered through Q Developer IDE plugins are included in the sunset timeline, so existing customers should complete or migrate transformation work before end of support.
- ✓AWS assistance and diagnostics: Existing Q Developer experiences can still support AWS service questions, troubleshooting, cost understanding, and operational guidance in supported first-party contexts.
Pricing
| Plan | Price | Key Features |
|---|---|---|
| Free | $0 | 50 agentic requests per month, Access latest Claude models, Use in the IDE or CLI, Reference tracking, Suppress public code suggestions, 1,000 LOC/month for Java upgrades |
| Pro | $19/user/month | Everything in Free, with increased limits, Increased agentic requests, 4,000 LOC/month for Java/.NET transformation, Identity center support with admin dashboards, IP indemnity, Automatically opted out of data collection |
Official pricing sources: aws.amazon.com · docs.aws.amazon.com · kiro.dev
Before You Pay
Decision check- ✓New Amazon Q Developer account and subscription signups are closed, so this page should be treated as a migration and continuity decision rather than a fresh purchase path.
- ✓IDE plugins and paid subscriptions are scheduled to reach end of support on 2027-04-30; plan migration work before that date rather than waiting for final support withdrawal.
- ✓AWS recommends Kiro for forward-looking developer workflows, but some Q Developer capabilities in first-party AWS surfaces continue outside the IDE and subscription sunset scope.
- ✓Existing customers should inventory active IDE, transformation, and AWS operational workflows separately because migration timing and replacement paths may differ by use case.
Pros & Cons
✅ Pros
- ✅ Existing AWS customers retain continuity during the transition window
- ✅ Deep integration with AWS services remains useful in supported first-party AWS experiences
- ✅ AWS provides a forward migration path to Kiro for developer workflows
- ✅ Existing transformation and operational use cases have a defined transition timeline
⚠️ Cons
- ⚠️ New Q Developer account and subscription signups are closed
- ⚠️ IDE plugins and paid subscriptions are scheduled to reach end of support on 2027-04-30
- ⚠️ New greenfield developer-tool adoption should evaluate Kiro instead
- ⚠️ Existing customers need an explicit migration plan for IDE and transformation workflows
Use Cases
Automating AWS Lambda Function Development
Developers can use Amazon Q Developer to automate the creation of AWS Lambda functions, significantly reducing development time and ensuring consistent code quality.
Streamlining AWS Resource Deployment
The tool helps in automating the deployment of AWS resources using CloudFormation, making the process efficient and less error-prone.
Enhancing Application Performance
By providing code analysis and suggestions, Amazon Q Developer aids in maintaining clean and efficient code, which can lead to improved application performance.
Accelerating Development Workflows
The automated features of Amazon Q Developer help developers focus on innovation rather than mundane coding tasks, accelerating the overall development workflow.
Alternatives
Frequently Asked Questions
Is Amazon Q Developer free?
Amazon Q Developer is no longer open to new account and subscription signups. Existing customers retain access during the transition period, while IDE plugins and paid subscriptions are scheduled to reach end of support on 2027-04-30. New developer-tool evaluations should review Kiro as AWS's forward migration path.
Do I need to use AWS to benefit from Q Developer?
While Q Developer shines brightest for AWS development, it's still a capable general-purpose coding assistant. However, if you don't use AWS at all, you may get more value from other AI coding tools that aren't AWS-specific.
What can the automated upgrade feature do?
The upgrade feature can transform legacy code to modern frameworks — for example, upgrading Java 8 to Java 17, migrating from .NET Framework to .NET Core, or updating Python 2 code to Python 3. It handles syntax changes, deprecated API replacements, and can even suggest architectural improvements.
How does security scanning work?
Q Developer scans your code for security vulnerabilities, including OWASP Top 10 issues, hardcoded credentials, SQL injection risks, and more. It provides detailed explanations of each vulnerability and suggests specific fixes with code examples.
What is the difference between Amazon Q Developer and GitHub Copilot?
While both are code assistance tools, Amazon Q Developer is specifically tailored for AWS services, offering contextually relevant assistance for AWS-based projects, whereas GitHub Copilot is a general-purpose tool offering code completion for various programming languages.
How much does Amazon Q Developer cost?
New Q Developer account and subscription signups are closed. Existing customers should review their current subscription and migration timeline rather than rely on a new-purchase price comparison; AWS recommends Kiro for forward-looking developer workflows.
Does Amazon Q Developer support all AWS services?
Amazon Q Developer supports a wide range of AWS services, including AWS Lambda, AWS API Gateway, and AWS RDS, but not all AWS services are currently supported.
Can I use Amazon Q Developer without being an AWS customer?
Yes, you can use Amazon Q Developer even if you are not an AWS customer, but some features may require an AWS account to function fully.
What is the learning curve like for Amazon Q Developer?
The learning curve for Amazon Q Developer can be steep, especially for users unfamiliar with AWS services. However, the user-friendly interface and extensive documentation can help new users get up to speed more quickly.
Are there any limitations to the Free tier of Amazon Q Developer?
Yes, the Free tier of Amazon Q Developer includes limited features and usage, which may not be sufficient for all development needs.