Exam-style
A company wants three things at once. Its engineers want help refactoring a legacy Java service and reading an unfamiliar CloudWatch error. Its staff want to ask questions that span SharePoint and the ticketing system, with each person seeing only what their existing permissions allow. And its product team wants a customer-facing assistant inside the company's own web application, grounded on the company's data. Which combination fits?
Reveal the answer
B. Amazon Q Developer for the engineers, Amazon Q Business for the staff-facing search, and Amazon Bedrock for the customer-facing assistant
Sort by who reads the output. Work aimed at engineers goes to a developer assistant: Amazon Q Developer refactors the legacy Java service, explains the unfamiliar CloudWatch error and generates the tests around the change, and Kiro covers the same developer productivity ground from the spec-driven side. Neither one indexes SharePoint or a ticketing system for the rest of the business. Work aimed at internal staff goes to Amazon Q Business, now sold under the Amazon Quick line, which brings managed connectors to enterprise sources and honours each user’s existing permissions on the documents it retrieves, so two people asking the same question get different answers. Only the third ask is a platform build: an assistant that ships inside the company’s own product, with its own interface, its own prompts and its own retrieval, belongs on Amazon Bedrock. That rules out the two options that put the customer-facing assistant on Amazon Q Business. Amazon Q Business Apps are lightweight internal tools that staff build over the same indexed corpus and share with colleagues, not a way to serve customers from someone else’s interface. It also rules out building all three on Bedrock, which means writing an IDE assistant and an enterprise search product AWS already sells finished, and it rules out pointing Kiro at SharePoint, which is not a surface Kiro serves.
Q. Engineers refactoring legacy Java, staff searching SharePoint and the ticketing system, and a customer-facing assistant inside your own product. Which surfaces?
A. Amazon Q Developer (or Kiro) for the engineers, Amazon Q Business for the staff, and Amazon Bedrock for the product feature.
Why? The audience for the output decides. Engineers get a developer productivity tool that lives in the IDE and the terminal. Internal staff get the managed enterprise assistant, Amazon Q Business under the Amazon Quick line, with connectors to SharePoint and the ticketing system and per-user permissions carried through to retrieval. Amazon Q Business Apps extend that to small internal tools staff assemble over the same index, still for colleagues. Customers are the only audience that needs a build: your interface, your prompts, your retrieval, on Bedrock.