Skip to main content

Amazon Web ServicesAI Coding Agent

Amazon Q Developer

AWS's generative AI assistant for building and operating on AWS. It offers inline suggestions and agentic chat in VS Code, JetBrains IDEs, Visual Studio, and Eclipse. Amazon Q also works in the AWS console, Slack, and Microsoft Teams. AWS's end-of-support notice closed new sign-ups on May 15, 2026, though its pricing page still offers them. Support for the IDE plugins and paid subscriptions ends April 30, 2027, and AWS points coding work to Kiro.

The 30-Second Take

Keep Amazon Q Developer only for the Pro seats you hold today, since AWS ends its IDE plugins on April 30, 2027.

Paid subscriptions end the same day, and new sign-ups closed in May 2026. Until then Pro keeps agentic chat in four IDEs, AWS billing, IAM Identity Center sign-in and IP indemnity.

Best fit
Teams already on Pro through IAM Identity Center that build on AWS and need a working assistant through April 2027.
Main constraint
No new Pro subscriptions since May 15, 2026, and the IDE plugins, Pro and code transformation end on April 30, 2027.
First move
Inventory Pro users, rules and transformation jobs, then run Kiro or another assistant on the same repositories this quarter.

Why

Watch the exit date, because the open question is where coding work goes next: AWS names Kiro, whose CLI already replaced the Q CLI. Teams not tied to AWS billing can weigh GitHub Copilot or Claude Code.

Practitioner sentiment, all practitioners+10 Mixed

39 practitioners, 84 sources reviewed, Updated Nov 1, 2026How this is measured

Read the GILD Review
Save a product your organization uses.Keep up with Amazon Q Developer without adding it to your stack.Visit Website
Operating stack
Agentic Software Development

Comparisons

How does Amazon Q Developer compare with the alternatives?

  1. Amazon Q Developer vs GitHub Copilot

    • AI Coding Agents

    Copilot is the one to buy: both team seats cost US$19 per user per month with IP indemnity in VS Code, JetBrains IDEs, Visual Studio, and Eclipse. Copilot adds GitHub.com agents and code review. Q Developer adds AWS console answers, takes no new sign-ups, and ends its IDE plugins on April 30, 2027.

  2. Amazon Q Developer vs Claude Code

    • AI Coding Agents

    Pick Claude Code for new agent work, since Q Developer's IDE plugins retire on April 30, 2027. Practitioners compared the Q CLI, now Kiro CLI, with Claude Code for a year. Claude Code runs in the terminal, VS Code, JetBrains, desktop, and web, and an AWS shop can bill it to AWS through Amazon Bedrock.

Operator Insights

What are engineering leaders learning from deploying Amazon Q Developer?

Buying and deployment

What engineering leaders should verify before a broader rollout.

Sourced from AWS documentation

How you buy it

US$19

Existing Pro only. AWS closed sign-ups May 15, 2026, while its pricing page still offers them.

Source 1, Amazon Web Services, Amazon Q Developer end-of-support announcement: Amazon Q Developer end-of-support announcementSource 2, Amazon Web Services, Amazon Q Developer pricing: Amazon Q Developer pricing

Details

AWS's end-of-support notice blocks new Free tier accounts through Builder ID and new Pro subscriptions in the console from May 15, 2026. AWS's pricing page, read on October 28, 2026, still offers a perpetual Free Tier and a Builder ID upgrade to Pro. Existing Pro subscriptions, US$19 per user per month billed to the AWS account and prorated in the first month, can still add users until end of support.

Cost drivers

1,000 user requests

A month on Pro, or 10,000 inference calls, with no overage. Free gets 50 agentic requests.

Source 2, Amazon Web Services, Amazon Q Developer pricing: Amazon Q Developer pricingSource 3, aws.amazon.com, Amazon Q Developer FAQs: Amazon Q Developer FAQs

Details

Each month, Free gets 50 agentic requests and 1,000 transformation lines; Pro gets about 1,000 user requests (10,000 inference calls) and 4,000 lines per user, pooled at the payer account. Free requests cover the IDE plugins and CLI. Pro requests have no overage, so a user who reaches the cap waits for the next month. Java upgrade transformation past the pool costs US$0.003 per line submitted, and canceling mid-month bills the full month.

Where it runs

IDEs and AWS apps

IDE plugins end April 30, 2027. The console, Slack, and Teams versions continue.

Source 1, Amazon Web Services, Amazon Q Developer end-of-support announcement: Amazon Q Developer end-of-support announcementSource 3, aws.amazon.com, Amazon Q Developer FAQs: Amazon Q Developer FAQs

Details

Plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse until April 30, 2027; Amazon Q in the AWS console, the Console Mobile Application, AWS websites, Slack, and Microsoft Teams, which continue. The Q CLI moves to Kiro CLI with q update, and the GitHub integration has not reached general availability.

What to verify

Training opt-out

Free tier content can train models, so opt every Free user out.

Source 3, aws.amazon.com, Amazon Q Developer FAQs: Amazon Q Developer FAQsSource 4, Amazon Web Services, Amazon Q Developer service improvement: Amazon Q Developer service improvementSource 1, Amazon Web Services, Amazon Q Developer end-of-support announcement: Amazon Q Developer end-of-support announcement

Details

That every Free tier user is opted out, through an AWS Organizations AI opt-out policy for the console and per IDE for plugins, since Free content can train models. Confirm where content is stored: Pro data stays in the Region where the Q Developer profile was created, and Free tier data in US Regions. Finish Java and .NET transformations before support ends.

Signals

What is the current evidence saying about Amazon Q Developer?

A current read of what engineering leaders, teams, and individual builders report publicly about Amazon Q Developer, with every finding linked to its sources.

Whose sources count

Practitioner sentiment, all practitioners

+10 Mixed net

of 43 sources that take a side, each author counted once.

How this figure is made

18 more state no overall view and cast no vote.

Leaders and teams have 6 accounts; GILD prints their sentiment from 20.

Current sentiment

Positive, mixed and negative sources

The score counts them as 16 positive, 11 mixed and 12 negative votes, one per author.

Across the 61 independent public accounts the read is mixed and leans positive: 18 positive, 12 mixed, and 13 negative; 18 state no overall view and cast no vote. Agentic coding draws the most consistent praise, from 15 of the 16 sources that discuss it. Every source discussing answer quality, bugs, or product direction raises a concern. Accounts that compare tools split 6 to 7 on their preferred main tool.

Use a task pilot to measure accepted work and review time.

Evidence field. All 84 sources, one mark each.

Arrange by

Each mark is one source: positive, mixed, negative, no opinion stated, or documentation (not counted).

By sentiment, All practitioners. Every source GILD read, grouped as the field draws it.
GroupSourcesPositiveMixedNegativeNo opinion stated and not counted in the scoreDocumentation, checked and not counted
Positive18180000
Mixed12012000
Negative13001300
Not counted27000270
Documentation14000014
Every source GILD read, by the quarter it was published, as the field's time axis counts it. Documentation is dated by the day it was checked.
QuarterSources
Q1 20259
Q2 202520
Q3 202519
Q4 202510
Q1 20262
Q2 20265
Q3 20265
Q4 20260
Documentation, checked14

By sentiment

14 documentation pages check facts and are not counted.

Hover a mark for a quick look, click it or press Enter to open its source.Tap a mark to open its source, then step to its neighbors with Previous and Next.

What practitioners praise

Top praise of 3. Each mark is a source on it; filled marks praise it.

  1. Agentic Coding15 of 16 sources on it praise it

Most common concerns

Top concern of 4. Each mark is a source on it; filled marks raise it.

  1. Answer QualityAll 10 sources on it raise it as a concern
All 84 sources behind these findings
  1. AWS DevOps Blog: Amazon Q Developer end-of-support announcement (Apr 30, 2026)Amazon Web Services (Official), Product documentation, checked Oct 12, 2026
  2. Amazon Q Developer docs: IDE plugins end of supportAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  3. Amazon Q Developer pricingAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  4. Amazon Q Developer docs: Tiers of service, Free and ProAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  5. Amazon Q Developer docs: Using Amazon Q Developer in the IDEAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  6. Amazon Q Developer docs: Using Amazon Q Developer on the command lineAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  7. Amazon Q Developer docs: Using Amazon Q Developer on AWS apps and websitesAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  8. Amazon Q Developer docs: Chatting with Amazon Q Developer in chat applicationsAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  9. Amazon Q Developer docs: Amazon Q Developer for GitHub (Preview)Amazon Web Services (Official), Product documentation, checked Oct 12, 2026
  10. Amazon Q Developer docs: Reviewing code with Amazon Q DeveloperAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  11. Amazon Q Developer docs: Service improvementAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  12. Amazon Q Developer docs: Data storageAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  13. Kiro docs: Migrating from Amazon Q DeveloperAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  14. Kiro docs: Upgrading from Q CLIAmazon Web Services (Official), Product documentation, checked Oct 12, 2026
  15. AWS Toolkit with Amazon Q extension on Visual Studio 2026 not installingbrosnanwong, GitHub user, self-described, GitHub issue, aws/aws-toolkit-visual-studio, published Sep 28, 2026
  16. Comment on: How accurate have Ed Zitron's AI skeptic predictions been?iLoveOncall, Amazon engineer (self-described: Personal use at home), Hacker News comment, published Sep 2, 2026
  17. bug: Ctrl+Z does not undo pasted prompts in Amazon Q VS CodeMathi-MS, GitHub user, self-described, GitHub issue, aws/amazon-q-developer-cli, published Aug 18, 2026
  18. Amazon Q automatically signs out mid-response in one specific projectefratroz-hub, GitHub user (self-described: Project shared with teammates), GitHub issue, aws/aws-toolkit-visual-studio, published Jul 26, 2026
  19. Amazon Q A big Bug or Error that is making it worthlessnishant-kumarbhatnag, GitHub user (self-described: Company-provided Q license, .NET Core in Visual Studio 2022 and 2026), GitHub issue, aws/aws-toolkit-visual-studio, published Jul 17, 2026
  20. Comment on: Codex logging bug may write TBs to local SSDsiLoveOncall, Amazon engineer (self-described: Amazon, outside the Kiro team), Hacker News comment, published Jun 22, 2026
  21. Trust commands to be executed without manually clicking on RUNitssamuelrowe, GitHub user, self-described, GitHub issue, aws/aws-toolkit-vscode, published Jun 16, 2026
  22. Always Allow option not persisted for MCP server toolsdeanis74, GitHub user, self-described, GitHub issue, aws/aws-toolkit-visual-studio, published May 1, 2026
  23. Amazon Q does not follow rulesjnothstine, GitHub user, self-described, GitHub issue, aws/aws-toolkit-visual-studio, published May 1, 2026
  24. Comment on: Small models also found the vulnerabilities that Mythos foundhibikir, Hacker News commenter (self-described: Team bug investigation with a tester), Hacker News comment, published Apr 11, 2026
  25. Comment on: Datadog, thank you for blocking us0xbadcafebee, Hacker News commenter (self-described: Operations support for internal teams), Hacker News comment, published Jan 11, 2026
  26. Comment on: Anthropic blocks third-party use of Claude Code subscriptionssirtaj, Hacker News commenter (self-described: Q and Kiro CLI at work), Hacker News comment, published Jan 9, 2026
  27. Comment on: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacymlaretallack, Hacker News commenter (self-described: Personal reverse-engineering project), Hacker News comment, published Dec 19, 2025
  28. Modernizing Java applications with AWS Q Developer: A journey from legacy to AI-powered developmentRohit Kumar Verma, Lead Consultant, Digital Business at HCLTech (HCLTech modernization team, a trial on two enterprise Java applications), Company blog post, HCLTech, published Dec 19, 2025
  29. AI-assisted software development with Amazon Q DeveloperMartin Heller, Contributing Writer at InfoWorld (Hands-on review in VS Code and the Q CLI, compared with Codex), Independent hands-on review, InfoWorld, published Dec 4, 2025
  30. Kiro CLI - is it OSS?kesor, r/aws member, self-described, Reddit post, r/aws, published Nov 19, 2025
  31. What's difference between Amazon Q developer CLI and Kiro CLIaviboy2006, r/aws member, self-described, Reddit post, r/aws, published Nov 19, 2025
  32. Comment on: AWS deprecates two dozen services (most of which you've never heard of)righthand, Hacker News commenter (self-described: Company AWS account with admin-managed Amazon Q access), Hacker News comment, published Nov 15, 2025
  33. How to allow all of the command execution in AWS Developer Q vscode extension?Litao82, r/aws member, self-described, Reddit post, r/aws, published Nov 8, 2025
  34. Comment on: I'm drowning in AI features I never asked for and I hate itchanux, Hacker News commenter (self-described: AWS console at work), Hacker News comment, published Oct 26, 2025
  35. Hallucinations, Bugs, and Speed in Amazon Q Developer CLI (AWS Gen AI)Mahdi Azarboon, r/aws member (self-described: AWS CDK TypeScript project), Reddit post, r/aws, published Oct 12, 2025
  36. Is there an AI strategy for AWS? Customers are confused and frustrated.Cultural_Village7083, r/aws member (self-described: Organization running its base compute and storage on AWS), Reddit post, r/aws, published Oct 11, 2025
  37. Amazon q dever Inline suggestion slowstrangerofnowhere, r/aws member (self-described: Team evaluating Q Developer), Reddit post, r/aws, published Sep 14, 2025
  38. Comment on: Show HN: Next Home Gamerichelectron, Hacker News commenter (self-described: Side project, self-hosted on a Raspberry Pi), Hacker News comment, published Sep 9, 2025
  39. Comment on: Amazonq.nvim: Official AWS AI Assistant Plugin for NeovimJCM9, Hacker News commenter, self-described, Hacker News comment, published Sep 3, 2025
  40. GitHub Copilot VS Amazon QPietro Maffi, Engineer building internal Jira reporting apps (self-described: Company where Copilot is the approved assistant), Practitioner article, dev.to, published Aug 26, 2025
  41. Comment on: We put a coding agent in a while loopdidibus, Hacker News commenter, self-described, Hacker News comment, published Aug 25, 2025
  42. Using Amazon Q Developer both CLI and extension, amazing for AWS infra/debugging, but code review feels like a gap. Anyone else?aviboy2006, r/aws member, self-described, Reddit post, r/aws, published Aug 11, 2025
  43. Has anyone tried this combination? AWS Q Developer + Superclaude FrameworkConsistent_Park5015, r/aws member (self-described: Organization that mainly uses AWS; junior engineer writing CDK), Reddit post, r/aws, published Jul 30, 2025
  44. Comment on: Warp.dev Terminal - Overpriced, Buggy, and AI-Sabotaged My Codensonha, Hacker News commenter, self-described, Hacker News comment, published Jul 28, 2025
  45. Amazon Q Developer (Pro/Free both) - Sonnet 4 Not available since FridayKitchen-Airport960, r/aws member, self-described, Reddit post, r/aws, published Jul 22, 2025
  46. Comment on: Kiro: A new agentic IDE__bjoernd, Hacker News commenter, self-described, Hacker News comment, published Jul 15, 2025
  47. Comment on: Kiro: A new agentic IDEtmvphil, Hacker News commenter, self-described, Hacker News comment, published Jul 15, 2025
  48. Comment on: Kiro: A new agentic IDEsmcleod, Hacker News commenter (self-described: DevOps practitioner, in tech since 2005), Hacker News comment, published Jul 15, 2025
  49. Giving AWS Q Developer CLI a second lookChris Ebert, software engineer at Tyler Technologies (self-described: Side project, a browser game built for the AWS Build Games Challenge; uses Claude Code at work), Personal blog post, chrisebert.net, published Jul 15, 2025
  50. Comment on: Kiro: A new agentic IDEdangus, Hacker News commenter, self-described, Hacker News comment, published Jul 14, 2025
  51. Comment on: Kiro: A new agentic IDEnullandvoid, Hacker News commenter (self-described: Workplace where Amazon Q was mandated, later replaced by Copilot), Hacker News comment, published Jul 14, 2025
  52. Comment on: AWS launches Kiro, its Cursor cloneWorldPeas, Hacker News commenter, self-described, Hacker News comment, published Jul 14, 2025
  53. Comment on: Kiro: A new agentic IDEplacardloop, Hacker News commenter, self-described, Hacker News comment, published Jul 14, 2025
  54. Comment on: Kiro: A new agentic IDEartdigital, Hacker News commenter, self-described, Hacker News comment, published Jul 14, 2025
  55. Comment on: Kiro: A new agentic IDEsmcleod, Hacker News commenter (self-described: DevOps practitioner, in tech since 2005), Hacker News comment, published Jul 14, 2025
  56. Post by Gergely Orosz on Amazon Q DeveloperGergely Orosz, author of The Pragmatic Engineer newsletter (self-described: Newsletter author reporting on engineering at Amazon), X post, published Jun 30, 2025
  57. Comment on: LLM code generation may lead to an erosion of trustgibspaulding, Hacker News commenter (self-described: Legacy C modules at work), Hacker News comment, published Jun 26, 2025
  58. Comment on: Gemini CLI0x457, Hacker News commenter, self-described, Hacker News comment, published Jun 25, 2025
  59. How do you set up Amazon Q Developer when the management account is a third-party organization?Legitimate-Yak-7742, r/aws member (self-described: Company inside a reseller's AWS Organization), Reddit post, r/aws, published Jun 18, 2025
  60. Comment on: Agentic Coding Recommendationsjpadamspdx, Hacker News commenter, self-described, Hacker News comment, published Jun 12, 2025
  61. Comment on: Why Cline Doesn't Index Your Codebase (and Why That's a Good Thing)MisterSandman, Hacker News commenter (self-described: University of Waterloo ECE, class of 2024), Hacker News comment, published May 27, 2025
  62. Comment on: Clojure MCPdidibus, Hacker News commenter, self-described, Hacker News comment, published May 27, 2025
  63. Comment on: MCP explained without hype or fluff0x457, Hacker News commenter, self-described, Hacker News comment, published May 22, 2025
  64. Comment on: Ask HN: Cursor or Windsurf?jsumrall, Hacker News commenter (self-described: Software engineer at Picnic), Hacker News comment, published May 12, 2025
  65. Comment on: Ask HN: Cursor or Windsurf?quintes, Hacker News commenter (self-described: Strategy and enterprise architecture advisor across APAC and the US West Coast), Hacker News comment, published May 12, 2025
  66. Amazon Q for GitHub: First ImpressionsJonathan LaCour, CTO at Mission Cloud (Own open-source video transcoding project, Squishy), Company blog post, Mission Cloud, published May 8, 2025
  67. The AI Pair Programmer in GitHub - Amazon Q Developer in GitHub (in preview)Vivek V., Developer; AWS Community Builder (self-described: Personal Medium-to-DEV converter tool), Practitioner article, dev.to (AWS Community Builders), published May 7, 2025
  68. Supercharging CloudThat’s Development and Security with Amazon QPrarthit Mehta, CTO of Cloud Consulting Services at CloudThat (CloudThat engineering teams with 53 active Amazon Q subscriptions), Company engineering blog post, CloudThat, published May 6, 2025
  69. Vibe Coding with Amazon Q Developer CLIPrateek Jain, r/aws member, self-described, Reddit post, r/aws, published Apr 26, 2025
  70. Comment on: AI Horseless Carriagesdangus, Hacker News commenter, self-described, Hacker News comment, published Apr 24, 2025
  71. Comment on: Amazon Q Developer releases state of the art agent for feature developmentzeristor, Hacker News commenter, self-described, Hacker News comment, published Apr 21, 2025
  72. Comment on: OpenAI Codex CLI: Lightweight coding agent that runs in your terminalnoidesto, Hacker News commenter, self-described, Hacker News comment, published Apr 17, 2025
  73. Comment on: OpenAI Codex CLI: Lightweight coding agent that runs in your terminalartdigital, Hacker News commenter, self-described, Hacker News comment, published Apr 17, 2025
  74. Comment on: AI coding mandates are driving developers to the brinkeestrada, Hacker News commenter, self-described, Hacker News comment, published Apr 9, 2025
  75. Agentic Q Developer First ImpressionsJonathan LaCour, CTO at Mission Cloud (CTO of an AWS consulting partner, one week alternating Q Developer CLI and Claude Code on one project), Company blog post, Mission Cloud, published Apr 3, 2025
  76. How Helpful and Secure can AI be? A Little Comparison of ChatGPT and Amazon Q DeveloperKarol Havrillay, Infrastructure engineer (self-described: Terraform for IAM, S3 and KMS), Practitioner article, dev.to, published Mar 31, 2025
  77. Comment on: "Vibe Coding" vs. Realitytrashtensor, Hacker News commenter, self-described, Hacker News comment, published Mar 22, 2025
  78. Comment on: Ikemen-GO: open-source reimplementation of MUGENdmacvicar, Hacker News commenter (self-described: Reviving an archived open-source game engine), Hacker News comment, published Mar 19, 2025
  79. Comment on: I've been using Claude Code for a couple of daysSamCritch, Hacker News commenter (self-described: Company Claude Code account with prepaid credit), Hacker News comment, published Mar 9, 2025
  80. AWS Chatbot's Rename to Amazon Q Developer is a Step BackwardCorey Quinn, Author of Last Week in AWS (self-described: Own AWS environment with chat alerts for console changes, cost anomalies and health events), Newsletter blog post, Last Week in AWS, published Feb 27, 2025
  81. Elevate Developer Experience with Generative AI Capabilities on AWSOlalekan Elesin, Engineering Director at HRS Group (Engineering organization on Azure SSO that ran GitHub Copilot before Q), Conference talk page with transcript, InfoQ Dev Summit Munich, published Feb 26, 2025
  82. Comment on: Microsoft cancels leases for AI data centers, analyst saysvel0city, Hacker News commenter (self-described: Employer-approved tooling; Python, Kubernetes, CDK), Hacker News comment, published Feb 24, 2025
  83. Comment on: Base-Rate Blindnesseightysixfour, Hacker News commenter, self-described, Hacker News comment, published Jan 26, 2025
  84. Grudgingly Accepting AI Coding AssistantsStephen A. Fuqua, Director, Software Engineering at Ed-Fi Alliance (Director evaluating coding assistants for open source engineering teams), Engineering director's blog post, Stephen A. Fuqua, published Jan 14, 2025

Jan 2025 to Sep 2026.

70 sources from practitioners, by month and sentiment.

The full readExplore all Amazon Q Developer Signals5 praise themes, 7 concerns, 1 point of agreement and 2 disagreements across all three groups, with all 84 sources open to inspect.

Where It Fits

Where does Amazon Q Developer belong in the stack?

Open Where It Fits: the Stack Field and the full map

Amazon Q Developer is Core across Build, supports Validate and Operate, and touches Plan and Ship.

Business area
Product & Engineering
Function
Software Development
Operating stack
Agentic Software Development
Primary role
AWS Coding Assistant, IDE Plugins Retiring
Amazon Q Developer beside the rest of its stackThe Stack Field, every product on every layer
FootprintAmazon Q Developer across the Agentic Software Development stack. Bar height is its role on each layer.

  1. Plan

    1. Work planning: Touches

      Work planning, touches. The GitHub integration implements labeled feature issues and opens pull requests. It is not yet generally available. The team keeps its backlog in an issue tracker.

  2. Build

    1. Codebase context: Supports

      Codebase context, supports. Chat reads open files, selected folders, and the indexed workspace. Rules in .amazonq/rules apply to every request. Deep search across repositories requires a code intelligence product.

    2. Coding: Core

      Coding, core. This is Q Developer's primary role: inline suggestions and agentic chat that reads files, writes diffs, and runs shell commands in VS Code, JetBrains IDEs, Eclipse, and Visual Studio. The IDE plugins are supported until April 30, 2027.

    3. Agent runtime: Core

      Agent runtime, core. Developers use the IDE plugins to chat with Q and approve actions or suggestions. The terminal agent became Kiro CLI on November 17, 2025.

    4. Tool execution: Supports

      Tool execution, supports. Q runs shell commands and MCP servers in the IDE. In the AWS console, it reads account resources and costs. The team's chosen agent or platform handles broader tool orchestration.

  3. Validate

    1. Debugging: Supports

      Debugging, supports. Amazon Q diagnoses common AWS console errors and answers resource and network-reachability questions, and IDE chat helps debug code. Production debugging stays with dedicated tools.

    2. Testing: Supports

      Testing, supports. Agentic chat writes and runs unit tests on request. The team's testing tools own the suites and end-to-end tests under its test strategy.

    3. Code review: Supports

      Code review, supports. IDE reviews flag quality and deployment risks and suggest fixes. The GitHub integration reviews new pull requests before general availability. A review tool or human reviewer owns approval.

    4. Application security: Supports

      Application security, supports. Code reviews in the IDE run SAST, secrets detection, infrastructure-as-code checks, and dependency analysis. Organization-wide scanning and policy stay with an application security product.

  4. Ship

    1. Source control: Touches

      Source control, touches. Q scopes reviews with git diffs. It works through GitLab Duo with Amazon Q and a GitHub integration before general availability. GitHub or GitLab owns branches and pull requests under the team's merge policy.

    2. CI/CD: Touches

      CI/CD, touches. Generated CDK, CloudFormation, and Terraform come from chat, and GitLab Duo with Amazon Q helps troubleshoot failed pipelines. Pipelines and deployments run in the team's CI/CD system.

  5. Operate

    1. Observability: Supports

      Observability, supports. In Slack and Microsoft Teams, Q answers resource, cost, and telemetry questions beside AWS alerts. CloudWatch investigations handles investigations. Observability tools own monitoring and paging.

Market mapThe layers Amazon Q Developer covers, and who else owns each one.

  1. Coding & implementation

    CoreBuild

  2. Agent interface & developer runtime

    CoreBuild

  3. Codebase context & intelligence

    SupportsBuild

  4. Tool execution & integrations

    SupportsBuild

  5. Debugging & investigation

    SupportsValidate

7 more layers on the full map. Core, Supports and Touches describe coverage. They say nothing about quality.

More on Amazon Q Developer

  1. GILD ReviewGILD's evaluation, with the buying facts
  2. Research2 pieces
  3. Guides3 guides
  4. Operator Insights1 operator account
  5. Where It FitsOn the Agentic Software Development stack
  6. Related Products7 products