Bedrock & Knowledge Base
A developer is building a customer support chatbot on Amazon Bedrock. It must handle multi-turn conversations, ground answers in product documentation stored in S3, never mention competitor products, minimize latency, and keep inference cost under $500/month for 10,000 conversations/day. Which architecture best satisfies all of these requirements?
A Knowledge Base backed by OpenSearch Serverless performs semantic retrieval over the S3 docs, and Haiku gives the lowest latency and cost among Bedrock models, fitting the budget. Guardrails' denied topics policy is the managed way to reliably suppress competitor mentions. Fine-tuning with provisioned throughput is costly overkill for grounding in existing docs. Pasting all documentation into the prompt blows past context limits and inflates per-request cost. Relying only on a system-prompt instruction to suppress competitor mentions is unreliable compared to a dedicated guardrail, and a relational lookup skips semantic search entirely.