How do we add context about relationships between tables (primary keys, foreign keys) and metadata like partition keys, sort keys to the knowledge base? Do we use the description feature within query configurations for this?
If the relationship is part of the schema then Bedrock will automatically get that information from the catalog. If it is not part of the schema then as you suggested the description feature within query configuration can be a good approach.
This seems like a permissions nightmare. You don't want all your users to have access to all of your database. I'm curious what controls if any could be put in place.
![AWS re:Invent 2024 - [NEW LAUNCH] Store tabular data at scale with Amazon S3 Tables (STG367-NEW)](http://i.ytimg.com/vi/1U7yX4HTLCI/mqdefault.jpg)
How do we add context about relationships between tables (primary keys, foreign keys) and metadata like partition keys, sort keys to the knowledge base? Do we use the description feature within query configurations for this?
If the relationship is part of the schema then Bedrock will automatically get that information from the catalog. If it is not part of the schema then as you suggested the description feature within query configuration can be a good approach.
@@SaketSaurabh Thank you, that makes sense
😊😊😊
😊😊
Can bedrock agents use a structured data knowledge base? I would love to add agent features like guardrails etc. on top of the kb features you demoed
Yes, this support will be available soon.
@ Thank you, looking forward for it!
This seems like a permissions nightmare. You don't want all your users to have access to all of your database. I'm curious what controls if any could be put in place.