Exam-style
Three requests land against the same Bedrock-backed summarisation service in one week. The front-end team wants a hosted web app with sign-in and a chat component wired to the backend, without hand-building the hosting, auth flow or API client. The partner integration team wants the request and response contract agreed and mocked so both sides can build before either writes code. An operations analyst wants to reorder a summarise-then-classify pipeline, and sometimes add a condition, without waiting on a release. Which set of tools fits the three asks in that order?
Reveal the answer
C. AWS Amplify for the front end, an OpenAPI specification for the partner contract, and Amazon Bedrock Flows for the analyst
Read each ask as what the asker is avoiding. The front-end team is avoiding hosting, sign-in and hand-written API clients, which is AWS Amplify: all three, plus a chat component bound to the backend. The partner team is avoiding two teams guessing at each other. An OpenAPI specification settles that: one document both sides generate clients, mocks and validation from. The analyst is avoiding the release train, which is Amazon Bedrock Flows: a canvas of prompt, condition and Lambda nodes, published as an immutable version with an alias moved to it. A Step Functions state machine is the tempting swap, since the pipeline is steps with a branch. But Step Functions has a visual editor too, in Workflow Studio, so drag-and-drop is not the difference. A flow models the prompts and the model calls themselves as nodes. Durable execution, retries and runs lasting hours would call for a state machine; nobody asked for those.
Q. A hosted chat UI with sign-in, an API contract agreed before either side codes, and a pipeline an analyst can reorder without a deployment. Three asks, one week. Which tool for which?
A. AWS Amplify for the hosted interface, an OpenAPI specification for the contract, and Amazon Bedrock Flows for the reorderable pipeline.
Why? Amplify removes the work between a working model call and a usable app: hosting, an auth flow, and a chat component from its AI kit that binds to a Bedrock-backed conversation route without a hand-rolled client. An OpenAPI document removes the wait between two teams. One contract generates mocks and clients, so both sides build in parallel and settle the response shape, including whether it streams before anyone writes the handler. Bedrock Flows removes the deployment from the loop for someone who is not shipping code: prompt, condition and Lambda nodes on a canvas, then an immutable version published and an alias moved to it. Reach for a Step Functions state machine when the pipeline needs durable execution, retries or a run measured in hours. Reach for Flows when the person reordering the pipeline is not the person who deploys the application.