The AI kit, generally available since November 2024, adds conversation and generation routes to an Amplify Gen 2 backend and a ready-made streaming chat component. Underneath: AppSync, a Lambda that calls Bedrock's Converse API, and DynamoDB for per-user history. What it gives you, what it costs, and when to build the same thing yourself.
Conversation routes: multi-turn, streaming chat with history scoped to the signed-in user, resumable across sessions.
Generation routes: single requests that return text or structured data, for summaries, extraction and form filling.
The AIConversation React component: a customizable chat interface that can render UI responses, not just text.
Tools backed by your Amplify Data queries, so the model can read the user's own data under the same authorization rules.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
AppSync handles the API and streaming to the client. A Lambda function bridges AppSync and Bedrock, calling the Converse API. DynamoDB stores conversations and messages per user. You pay for each of those plus the Bedrock model, and there is no separate charge for the kit.
Use it for a chat or summarization feature inside an Amplify app, where per-user history and auth matter and speed of delivery matters more than control.
Build it yourself when you need a different model provider or gateway, complex agent loops, evaluation pipelines or retrieval beyond what tools over Amplify Data provide. The architecture is simple to reproduce in CDK.
Either way, add the basics the demo omits: per-user rate limits, logging of prompts and responses for evaluation, and an eval set before changing models.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Leaving AWS Amplify and AppSync: When It Is Time, and How to Do It Without a Rewrite
Amplify gets a startup to launch fast. The trouble starts later: list queries that scan, resolvers that can't throw or call out, a 30-second ceiling, and a data model that was never designed. The signs it is time to leave, what to move to, what to keep, and a cutover that doesn't log anyone out.
Read
Using the Amplify Libraries Without an Amplify Backend: Cognito, AppSync and S3 You Already Have
The Amplify client libraries and UI components work against AWS resources created any way you like: CDK, Terraform or the console. How to point them at an existing Cognito user pool, AppSync API or S3 bucket, what you gain (sign-in screens, token refresh, signed uploads) and what you give up.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.