UI fails when Knownledge Bases for Bedrock is configured with a non S3 vector stiore and use case configuration is set to display source links #131
Labels
bug
Something isn't working
Comments
|
We are working on fixing this issue. |
tabdunabi
added a commit
that referenced
this issue
Aug 19, 2024
### Changed - With the release of [AWS-Solutions-Constructs v2.65.0](https://github.com/awslabs/aws-solutions-constructs/tree/main/source/patterns/%40aws-solutions-constructs/aws-apigatewayv2websocket-sqs), the AWS ApiGateway websocket integration with Amazon SQS Queue is available in the library. Hence the implementation has been updated to use this construct. ### Fixed - Issue [#131](#131) which caused an issue with rendering non-S3 source URLs from vector store for a RAG based use case. - Issue [#132](#132) where configured Guardrails for Amazon Bedrock to have no effect on a use case's text input validations and output responses. - Wizard validation failure for SageMaker model selection type, that allowed user to navigate ahead even when the page had failed validations. - An AWS WAF rule that blocked larger payloads for HTTP POST request to the `/deployments` endpoint. This restricted configuring large system prompts (over 8 KB) for use case cases. By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
tabdunabi
added a commit
that referenced
this issue
Aug 19, 2024
### Changed - With the release of [AWS-Solutions-Constructs v2.65.0](https://github.com/awslabs/aws-solutions-constructs/tree/main/source/patterns/%40aws-solutions-constructs/aws-apigatewayv2websocket-sqs), the AWS ApiGateway websocket integration with Amazon SQS Queue is available in the library. Hence the implementation has been updated to use this construct. ### Fixed - Issue [#131](#131) which caused an issue with rendering non-S3 source URLs from vector store for a RAG based use case. - Issue [#132](#132) where configured Guardrails for Amazon Bedrock to have no effect on a use case's text input validations and output responses. - Wizard validation failure for SageMaker model selection type, that allowed user to navigate ahead even when the page had failed validations. - An AWS WAF rule that blocked larger payloads for HTTP POST request to the `/deployments` endpoint. This restricted configuring large system prompts (over 8 KB) for use case cases. By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
|
This issue has been resolved in GAAB v2.0.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A use case configured with non s3 vector store and display source link enabled, throws an error.
To Reproduce
Steps to reproduce the behavior.
Configure a use case with Knowledge bases for Bedrock. Configure a non S3 vector store. Create a use case with RAG and use this knowledge base. Also configure display source links. The chat UI after the first response fails and shows a white screen.
Expected behavior
A clear and concise description of what you expected to happen.
Please complete the following information about the solution:
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: