An AWS Machine Learning blog post guides builders choosing a customer-managed vector store for Amazon Bedrock Knowledge Bases, comparing Amazon OpenSearch Service, Amazon Aurora PostgreSQL with pgvector, and Amazon S3 Vectors across three RAG use cases. It includes original benchmarks on OpenSearch Serverless Classic collections using Amazon's ESCI shopping dataset, measuring NDCG@10, latency, and index size across embedding dimension and data type configurations. The guidance helps practitioners trade off latency, cost, and search quality when building RAG on AWS.
A developer posted a practical guide on building reliable RAG applications on AWS using Amazon Bedrock, shared on Reddit for community feedback. The guide emphasizes engineering considerations for production—retrieval quality, chunking, evaluation—over introductory explanations, making it a practitioner-focused resource for teams building on AWS.
A developer posted a practical guide on building reliable RAG applications on AWS using Amazon Bedrock, shared on Reddit for community feedback. The guide emphasizes engineering considerations for production—retrieval quality, chunking, evaluation—over introductory explanations, making it a practitioner-focused resource for teams building on AWS.
AWS published a technical how-to for building an insurance claims assistant on Amazon Bedrock Knowledge Bases, using agentic retrieval to answer natural-language questions over claim documents with citations. The guide combines S3-indexed claim files, metadata filtering, Guardrails grounding checks, and multi-turn conversation. A 40-question evaluation on synthetic data showed 90.5% retrieval recall and 81.2% citation recall.
AWS published a technical how-to for building an insurance claims assistant on Amazon Bedrock Knowledge Bases, using agentic retrieval to answer natural-language questions over claim documents with citations. The guide combines S3-indexed claim files, metadata filtering, Guardrails grounding checks, and multi-turn conversation. A 40-question evaluation on synthetic data showed 90.5% retrieval recall and 81.2% citation recall.
AWS announced general availability of TwelveLabs Marengo Embed 3.0 as an embedding model in Amazon Bedrock Knowledge Bases, enabling natural language search over video, audio, and image assets without custom pipelines. The managed service handles segmentation, frame sampling, transcription, and embedding automatically, removing the need to stitch together transcription services, frame extraction, vector databases, and sync logic.
AWS announced general availability of TwelveLabs Marengo Embed 3.0 as an embedding model in Amazon Bedrock Knowledge Bases, enabling natural language search over video, audio, and image assets without custom pipelines. The managed service handles segmentation, frame sampling, transcription, and embedding automatically, removing the need to stitch together transcription services, frame extraction, vector databases, and sync logic.
An AWS Storage Blog post walks through implementing Amazon S3 Vectors as a custom persistent memory provider for NVIDIA's NeMo Agent Toolkit (NAT), deployed on Amazon EKS using a multi-agent investment research use case. It covers NAT's memory plugin interface, the auto_memory_agent workflow, multi-agent memory sharing via metadata filters, and operational deployment patterns. Practitioners get a concrete recipe for production agent memory with elastic vector storage, strong write consistency, and IAM-based isolation.
An AWS Storage Blog post walks through implementing Amazon S3 Vectors as a custom persistent memory provider for NVIDIA's NeMo Agent Toolkit (NAT), deployed on Amazon EKS using a multi-agent investment research use case. It covers NAT's memory plugin interface, the auto_memory_agent workflow, multi-agent memory sharing via metadata filters, and operational deployment patterns. Practitioners get a concrete recipe for production agent memory with elastic vector storage, strong write consistency, and IAM-based isolation.
AWS published two posts on building agentic retrieval with Managed Amazon Bedrock Knowledge Bases: one on observability for enterprise agentic retrieval using AWS CloudFormation, and one on multi-tenant agentic chat over enterprise data. Both target the step beyond single-source RAG, where an agent routes questions across knowledge bases and retrieves iteratively. The multi-tenant post emphasizes per-tenant document isolation enforced from verified identity rather than client-supplied values.
AWS published two posts on building agentic retrieval with Managed Amazon Bedrock Knowledge Bases: one on observability for enterprise agentic retrieval using AWS CloudFormation, and one on multi-tenant agentic chat over enterprise data. Both target the step beyond single-source RAG, where an agent routes questions across knowledge bases and retrieves iteratively. The multi-tenant post emphasizes per-tenant document isolation enforced from verified identity rather than client-supplied values.