What happened to Amazon Q Developer?
In short
Access changed on .
From AWS blocks new Q Developer Free accounts and new subscriptions; existing customers keep access, with IDE plugins and paid subscriptions supported until .
Source: AWS DevOps blog.
What this means
On , Amazon Web Services blocked new Amazon Q Developer Free accounts and new paid subscriptions, while existing paid subscriptions could still add users. IDE plugins and paid subscriptions remained supported through , but Q Developer in the AWS console, mobile app, documentation, website, Slack, and Teams was not part of this sunset. AWS told IDE users to move to Kiro and review its migration guide.
What to use now
Amazon Web Services points users to Kiro.
Looking for another coding tool? We list 20 AI coding tools with checked facts.
Changes to Amazon Q Developer
- Access changed on . From AWS blocks new Q Developer Free accounts and new subscriptions; existing customers keep access, with IDE plugins and paid subscriptions supported until . Source: AWS DevOps blog.
- Renamed on . Amazon Q Developer CLI: AWS updated Amazon Q Developer CLI to Kiro CLI on (v1.20.0); the start command changed to kiro-cli and configuration file paths changed. Source: AWS blog (Japanese).
More changes from Amazon Web Services
- AWS Chatbot: Renamed on