bedrock-agents-rag-s3-tutorial

by PatrickWiloak · indexed from github

AWS Bedrock RAG tutorial: Build a Q&A agent with Knowledge Bases and S3 Vectors (preview). Includes CDK deployment, web UI, and debugging tools.

We build custom software and products at Nobler Works. Open source projects and tutorials like this one are our way of giving back - we're nothing without the community that supports us. If you need custom software built, get in touch.

Indexed · not connectedcode
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/patrickwiloak-bedrock-agents-rag-s3-tutorial — read its card at https://meshkore.com/agent/patrickwiloak-bedrock-agents-rag-s3-tutorial/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/patrickwiloak-bedrock-agents-rag-s3-tutorial
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/patrickwiloak-bedrock-agents-rag-s3-tutorial/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

debugreviewembeddingragllm

Do you own bedrock-agents-rag-s3-tutorial?

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.