Amazon Pharmacy Uses Amazon SageMaker to Build an LLM-Based Customer Care Chatbot
Amazon Pharmacy created a question and answering chatbot assistant for customer care agents using large language models to improve information retrieval in a complex, highly regulated healthcare environment. The solution uses AWS services including Amazon SageMaker JumpStart, Amazon ECS, Amazon S3, Amazon OpenSearch Service, and Amazon Fargate to build a HIPAA-compliant, secure, and scalable chatbot. The chatbot empowers agents to find precise pharmacy information quickly, improving customer interactions while maintaining human judgment and feedback for continuous improvements.
- Organization
- Amazon Pharmacy
- Industry
- Healthcare
- Location
- United States
- Published
- October 2023
Why do we believe this deployment?Customer identity, provider attribution, maturity, and source checks
- Customer
- Amazon Pharmacy
- Provider
- AWS
- Maturity
- Production
- Linked source
- AWS Machine Learning Blog
Deployed the solution in a microservices architecture on Amazon ECS and Fargate with network isolation and compliance controls
Primary read
Use case focus
Showing 3 of 3
- 1Question Answering
- 2Customer Support Automation
- 3Generative AI
- Developed an AI-powered question and answering chatbot using foundation models in Amazon SageMaker JumpStart to accelerate development.
- Implemented the Retrieval Augmented Generation (RAG) pattern combining embedding-based search with generative large language model responses via Amazon OpenSearch Service and SageMaker endpoints.
- Deployed the solution in a microservices architecture on Amazon ECS and Fargate with network isolation and compliance controls.
- Incorporated a feedback loop enabling agents to provide feedback on answers for ongoing model improvement.
Architecture
Architecture consists of a microservices deployment in isolated VPCs using Amazon ECS, Fargate, S3 for knowledge base storage, SageMaker endpoints hosting embedding and LLM models, and OpenSearch for vector similarity search. PrivateLink is used for secure communication between components.
Sources & evidence1
- Customer explicitly identified
- Deployment status explicitly supported
- Technical implementation details available
The same organization appears in newer AI deployment evidence.
- Same organization re-documented as recently as 2026.
Measures whether this deployment's public evidence persists — not whether the system is still in production.
AI-generated summary. Verify important details with the linked sources before relying on this case.
Explore related AI use cases
Was this useful?
Community
Comments
No published comments yet.