Exam-style
A company's engineers want to move a legacy Java 8 service to Java 17, and to understand an unfamiliar Lambda error in the console. Its staff want to ask questions that span SharePoint and the ticketing system, with each person seeing only what their permissions allow. Its product team wants a customer-facing assistant inside the company's own web application, grounded on company data. Which combination fits?
Reveal the answer
B. Amazon Q Developer or Kiro for the engineers, Amazon Quick 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 transforms Maven-built Java 8 projects to Java 17 in the IDE, and diagnoses Lambda, EC2, ECS, S3 and Step Functions errors in the console. Kiro covers the same ground from the spec-driven side, and AWS ends support for the Q Developer IDE plugins on 30 April 2027. Neither indexes SharePoint for the rest of the business. Work aimed at internal staff goes to Amazon Quick, since Amazon Q Business held that role and is closed to new customers. Quick indexes SharePoint document libraries as a knowledge base, applies document-level ACLs under the admin-managed setup, and reaches ServiceNow or Jira through an action connector. Only the third ask is a platform build: an assistant inside the company’s own product, with its own interface, prompts and retrieval, belongs on Amazon Bedrock. An app in Quick renders inside Quick and needs a Quick subscription per reader, so it serves colleagues rather than customers. Building all three on Bedrock means writing an IDE assistant and an enterprise search product AWS already sells finished.
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 Quick for the staff, and Amazon Bedrock for the product feature.
Why? The audience for the output decides. Engineers get a developer assistant that sits in the IDE and the console, though AWS ends support for the Amazon Q Developer IDE plugins on 30 April 2027 and directs that work to Kiro. Internal staff get the managed enterprise assistant, Amazon Quick: it indexes SharePoint document libraries, reaches a ticketing system such as ServiceNow or Jira through an action connector, and applies document-level ACLs on the sources that support them. Amazon Q Business held that role and is closed to new customers now. Customers are the only audience that needs a build: your interface, your prompts, your retrieval, on Bedrock.