-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Add special handling of bedrock-runtime service in service router #11706
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
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 3m 32s ⏱️ Results for commit b54fd87. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have an automated test which basically tests every single possible endpoint.
For bedrock, this is currently disabled because it did not work.
Would be great to remove this exclusion to verify that your fix actually works.
Afterwards we should be good to go! 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 🤖 LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thanks for enabling bedrock in the service router tests! This way we can be sure that (a) every routing in the service really works, and (b) there are no regressions due to newly introduced services causing new routing ambiguities. :)
Motivation
As
bedrock
andbedrock-runtime
have the same signing namebedrock
,bedrock-runtime
requests are directed to the/model
path. This is similar to howsagemaker-runtime
also works.Changes
bedrock
to send requests to/model/
and/guardrail/
to thebedrock-runtime
provider.bedrock
andbedrock-runtime