Skip to main content

Decision brief

Amazon Q Developer Review: What Existing AWS Customers Should Do Before April 2027

Keep Q Developer Pro running while you move IDE work to Kiro before April 30, 2027. Amazon Q stays in the AWS console and chat apps.

Reading time
3 min read
Sources
23 cited
In this piece
Amazon Q Developer+10 Mixed

GILD verdict

Keep Q Developer for teams already on Pro, since no new team can buy it, and set a dated plan to move IDE coding work and transformation jobs before April 30, 2027.

Keep Amazon Q in the AWS console, which AWS continues.

Amazon Q Developer

AI Coding Agent by Amazon Web Services

+10 Mixed
Product page

Fit and limits

Who it fits

  • Your engineers already hold Pro seats through IAM Identity Center and you want the plugins they use in VS Code, JetBrains IDEs, Visual Studio, or Eclipse to keep working through April 2027. AWS keeps pushing critical bug fixes until then.
  • Your teams build on AWS and use Amazon Q in the console to ask about resources and costs and to diagnose console errors, which continues after the IDE plugins end.
  • Legal requires that seat content stay out of training and that generated output carry indemnity. Pro content is excluded from service improvement, and Section 50.10 of the AWS Service Terms covers Amazon Q except the Free tier.
  • You want questions about AWS resources and costs answered inside Slack or Microsoft Teams channels, which AWS also continues.

Where it falls short

  • AWS's end-of-support notice blocked new Free tier sign-ups through Builder ID and new subscriptions in the console on May 15, 2026, while its pricing page still offers both. Organizations with an active Pro subscription can still add users; any other team should confirm with AWS in writing before it starts.
  • AWS removed Claude Opus 4.6 from Pro on May 29, 2026 and offers its newest coding models, including Opus 4.7, only in Kiro.
  • The Q CLI became Kiro CLI on November 17, 2025, and new command-line features and fixes ship only there.
  • Pro agentic use stops at a monthly cap with no overage. AWS's FAQ puts the cap at 10,000 inference calls, about 1,000 user requests, after which a user waits for the next month.

Implementation reality

  1. Inventory what depends on Q

    List Pro users and the accounts they are subscribed in, rules files under .amazonq/rules, MCP configurations, customizations, and any pipeline or GitLab and GitHub workflow that calls Q. AWS states that automations depending on the IDE plugins and paid subscriptions stop on April 30, 2027.

  2. Finish transformations early

    Java upgrades and .NET porting through the IDE plugins end with the subscriptions. Pro includes 4,000 lines per user per month pooled at the payer account, so schedule the remaining jobs now and move later modernization to AWS Transform, which AWS recommends.

  3. Close the Free tier data gap

    Free tier content can be used for service improvement and model training. Opt out the console, mobile app, websites, and chat apps with an AWS Organizations AI services opt-out policy. Have every IDE user on Free turn off content sharing in the plugin settings.

  4. Pilot the successor on real work

    Run Kiro, or the assistant you would standardize on instead, on the same repositories your Q users work in. Kiro CLI still reads .amazonq folders in projects, Kiro IDE imports VS Code profiles, and both Kiro IDE and Kiro CLI accept Q Developer Pro subscriptions. Administrators upgrade users and groups to Kiro plans in the console, in bulk if needed, and AWS states the upgrade cannot be reversed.

  5. Keep review where it is

    Q's IDE code reviews and GitHub reviews flag issues for a human to accept. Keep CI and a human approval on every change Q writes, and record which review checks you will need to replace when the plugins end.

What to measure in your pilot

  • Run each Pro group's usual work on Kiro for a sprint and price the group at Kiro Pro, US$20 with 1,000 credits, or Pro+ at US$40, from the credits it burns.
  • GILD found no end date for Amazon Q Developer for GitHub in AWS's end-of-support notice, FAQ, or GitHub docs; get one from your account team before a pipeline depends on it.

Sources

Official documentation
22
Public source
1
  1. AWS DevOps Blog: Amazon Q Developer end-of-support announcement (Apr 30, 2026)Official documentationaws.amazon.com
  2. Amazon Q Developer docs: IDE plugins end of supportOfficial documentationdocs.aws.amazon.com
  3. Amazon Q DeveloperOfficial documentationaws.amazon.com
  4. Amazon Q Developer pricingOfficial documentationaws.amazon.com
  5. Amazon Q Developer docs: What is Amazon Q Developer?Official documentationdocs.aws.amazon.com
  6. Amazon Q Developer docs: Tiers of service, Free and ProOfficial documentationdocs.aws.amazon.com
  7. Amazon Q Developer docs: Using Amazon Q Developer in the IDEOfficial documentationdocs.aws.amazon.com
  8. Amazon Q Developer docs: Using Amazon Q Developer on the command lineOfficial documentationdocs.aws.amazon.com
  9. Amazon Q Developer docs: Using Amazon Q Developer on AWS apps and websitesOfficial documentationdocs.aws.amazon.com
  10. Amazon Q Developer docs: Chatting with Amazon Q Developer in chat applicationsOfficial documentationdocs.aws.amazon.com
  11. Amazon Q Developer docs: Amazon Q Developer for GitHub (Preview)Official documentationdocs.aws.amazon.com
  12. Amazon Q Developer docs: GitLab Duo with Amazon QOfficial documentationdocs.aws.amazon.com
  13. Amazon Q Developer docs: Reviewing code with Amazon Q DeveloperOfficial documentationdocs.aws.amazon.com
  14. Amazon Q Developer docs: Service improvementOfficial documentationdocs.aws.amazon.com
  15. Amazon Q Developer docs: Data storageOfficial documentationdocs.aws.amazon.com
  16. Amazon Q Developer docs: Cross-region processingOfficial documentationdocs.aws.amazon.com
  17. AWS Organizations docs: AI services opt-out policiesOfficial documentationdocs.aws.amazon.com
  18. AWS Service Terms (Section 50, Amazon Q and Kiro)Official documentationaws.amazon.com
  19. Kiro docs: Migrating from Amazon Q DeveloperOfficial documentationkiro.dev
  20. Kiro docs: Upgrading from Q CLIOfficial documentationkiro.dev
  21. Kiro pricingOfficial documentationkiro.dev
  22. AWS: Amazon Q Developer FAQs (Kiro and pricing sections)Official documentationaws.amazon.com
  23. SWE-bench: Verified leaderboard (Amazon Q Developer Agent, Apr 2025 submission)Public sourceswebench.com

Keep reading

  1. Buyer guideAmazon Q Developer Workflow Playbook: Rules, Approvals, and Reviewed ChangesHow teams still on Q Developer brief it with project rules, limit agentic chat to approved tools and read-only AWS roles, and review its changes and findings before merge.
  2. Buyer guideAmazon Q Developer Data, Region, and Indemnity ChecklistWhich tier trains on your content, where each feature stores it, how to opt an organization out, and what the AWS Service Terms indemnity covers.
  3. Buyer guideMoving from Amazon Q Developer to KiroWhat changes for Q Developer CLI and IDE plugin users, how Q Developer Pro seats map to Kiro tiers, and which transformation jobs to finish. Both plugins and paid subscriptions end on April 30, 2027; settle the move before then.
Read the research