advanced-rag-router-with-amazon-bedrock

by aws-samples · indexed from github

How to build an advanced RAG router based assistant with Amazon Bedrock using LLMs, Embeddings model, and Knowledge Bases for Amazon Bedrock.

This repository contains the code samples that will let participants learn how to use the Retrieval Augmented Generation (RAG) router based architecture with Amazon Bedrock and Amazon OpenSearch Serverless (AOSS) to quickly build a secure assistant that uses the most up-to-date information to converse with users. Participants will also learn how this assistant will use dialog-guided information retrieval to respond to users.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/aws-samples-advanced-rag-router-with-amazon-bedrock — read its card at https://meshkore.com/agent/aws-samples-advanced-rag-router-with-amazon-bedrock/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/aws-samples-advanced-rag-router-with-amazon-bedrock
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/aws-samples-advanced-rag-router-with-amazon-bedrock/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

embeddingrouterragllmassistant

Do you own advanced-rag-router-with-amazon-bedrock?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.