Key findings
- The end of support covers the IDE plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse, the Pro subscription, and Java and .NET transformation through the plugins.
- Sign-ups closed on May 15, 2026. AWS blocks new Free tier accounts through Builder ID and new subscriptions in the console, and existing Pro subscriptions can still add users.
- Amazon Q stays in the AWS Management Console, the documentation and marketing sites, the Console Mobile Application, Slack, and Microsoft Teams.
- AWS still ships the plugins. The VS Code extension reached version 2.8.0 on October 1, 2026 and showed about 1.88 million installs on October 28, 2026, with the end-of-support notice at the top of its listing.
Plan the move of every IDE user to Kiro or another assistant now. AWS gave a year's notice on April 30, 2026, after earlier steps in the same direction. Java transformation left the GitHub integration on December 15, 2025 and GitLab Duo on January 16, 2026, and newer models went to Kiro only.
What ends, and when
AWS announced the April 30, 2027 deadline in its April 30, 2026 DevOps Blog post, giving customers about 12 months. Critical bug fixes continue until then. The four IDE marketplaces retain the plugins with deprecation notices. AWS says dependent automations, including pipelines and scans, stop at end of support.
Java upgrades and .NET porting through the IDE plugins also end on April 30, 2027. AWS recommends completing active jobs before then and using AWS Transform for later modernization.
- November 17, 2025: the Q CLI becomes Kiro CLI. Users with auto-update move on November 24, 2025.
- December 15, 2025: AWS deprecates Java transformation in Amazon Q Developer for GitHub.
- January 16, 2026: GitLab Duo with Amazon Q loses Java transformation.
- April 30, 2026: AWS announces that the IDE plugins and paid subscriptions will end.
- May 15, 2026: new Free tier sign-ups through Builder ID and new Pro subscriptions are blocked.
- May 29, 2026: Claude Opus 4.6 leaves Pro. Opus 4.5 and other models remain, and newer models such as Opus 4.7 are Kiro only.
- April 30, 2027: end of support for the IDE plugins, paid subscriptions, and transformation through the plugins.
What stays
Amazon Q in the AWS console continues to answer questions about AWS services and account resources and costs. It also diagnoses common console errors. Slack and Microsoft Teams retain Free-tier answers beside AWS notifications. Teams using Q for AWS operations can keep it.
AWS renamed AWS Chatbot to Amazon Q Developer in chat applications in February 2025. In June 2025, it moved Q Developer operational investigations into CloudWatch under the name CloudWatch investigations.
Where the work goes
AWS directs IDE users to Kiro. VS Code users can import a profile into Kiro IDE. JetBrains users can run Kiro CLI through JetBrains AI Assistant. Visual Studio and Eclipse users must use a separate Kiro IDE or CLI because neither has a Kiro plugin.
Q Developer Pro subscriptions work in Kiro CLI. Administrators can upgrade individuals or groups to Kiro subscriptions. AWS output indemnity covers paid Kiro tiers and Pro. Teams without an AWS billing requirement can use the April 2027 deadline to evaluate other assistants.
Methodology
GILD built this record from AWS's own pages, checked on October 12, 2026. These cover the end-of-support announcement, the user guide's end-of-support page and document history, and pricing. They also include the AWS Service Terms, the Kiro migration guides, and the Visual Studio Marketplace listing. Install counts and version dates are the marketplace's figures on that day.
Products in this piece
Sources
- Official documentation
- 14
- AWS DevOps Blog: Amazon Q Developer end-of-support announcement (Apr 30, 2026)
- Amazon Q Developer docs: IDE plugins end of support
- Amazon Q Developer docs: Document history
- Amazon Q Developer pricing
- Amazon Q Developer
- Amazon Q Developer docs: Using Amazon Q Developer on AWS apps and websites
- Amazon Q Developer docs: Chatting with Amazon Q Developer in chat applications
- Amazon Q Developer in chat applications: Document history
- Amazon Q Developer docs: Using Amazon Q Developer on the command line
- AWS Service Terms (Section 50, Amazon Q and Kiro)
- Kiro docs: Migrating from Amazon Q Developer
- Kiro docs: Upgrading from Q CLI
- Visual Studio Marketplace: Amazon Q
- JetBrains Marketplace: Amazon Q