-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bedrock_agent_runtime APIs are not returning source metadata #4124
Comments
Hi @adoyon23 thanks for reaching out. The Agents for Amazon Bedrock Runtime APIs are called when using the corresponding Boto3 commands. Therefore we would need to escalate this issue to the service team to investigate issues as to why the expected metadata is not being returned. I created a new issue to track this in our cross-SDK repository going forward, since service APIs like this are used across AWS SDKs: aws/aws-sdk#746. Please refer to that issue for updates going forward. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
When I call the
invoke_agent
,retrieve
, orretrieve_and_generate
APIs for thebedrock_agent_runtime
, the response never contains the metadata keys associated with the source files. I know that the metadata is set up correctly for the source, because I see it show up in the vector DB indexes, and if I test the knowledge base directly in the console and view the trace, it shows the correct source metadata.However, when I call any of the APIs mentioned above referencing the same knowledge base, the response never contains the source metadata information.
Expected Behavior
The
retrievedReferences
key in the response from aninvoke_agent
call to thebedrock_agent_runtime
should contain ametadata
key whose values match the JSON key values set in the corresponding source.metadata.json
file.Current Behavior
There is no
metadata
key returned by any of theinvoke_agent
,retrieve
, orretrieve_and_generate
APIs.Reproduction Steps
Call the
invoke_agent
API similar to the code below with redacted info:Possible Solution
No response
Additional Information/Context
No response
SDK version used
boto3-1.34.99
Environment details (OS name and version, etc.)
Mac OS 14.4.1 (23E224), Python 3.12 runtime for AWS Lambda
The text was updated successfully, but these errors were encountered: