-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[DO NOT MERGE] Amazon Bedrock AgentCore exploration - WebSocket edition #3128
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
base: main
Are you sure you want to change the base?
Conversation
| // endpoint: 'http://localhost:7860/connect', | ||
| // }); | ||
| const aws = new AwsClient({ | ||
| accessKeyId: "<YOUR_ACCESS_KEY>", |
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.
These need to be filled in
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
| # TODO: clean up. Hackily overrides transport created by bot() entrypoint... | ||
| ws_transport = WebsocketServerTransport( | ||
| # host=public_ip, | ||
| port=8080, # This is the only port we're allowed to bind to...but the problem is it's already taken in order to support the /invoke HTTP entrypoint. |
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.
Here's the crux of the problem. Port 8080 is already being used to expose the invoke method, which starts the bot (which sets up the pipeline, etc.)
The thing to try next, which is a bit more complicated, is to make it so:
- We don't use the default app entrypoint (
@app.entrypoint) - we may have to abandon usingBedrockAgentCoreAppentirely. - Instead, on the
if __name__ == "__main__"section, we set up a WebSocket server on port 8080 - Only when we connect we kick off the code to set up the Pipecat pipeline...
- ...and somehow pass that already-established connection to use as the Pipecat WebSocket transport
No description provided.