-
Notifications
You must be signed in to change notification settings - Fork 51
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: error attaching same action group to multiple agents #747
Comments
mccauleyp
added
bug
Something isn't working
needs-triage
This issue or PR still needs to be triaged.
labels
Oct 14, 2024
github-project-automation
bot
moved this to Backlog
in AWS Generative AI Constructs Backlog
Oct 14, 2024
2 tasks
krokoko
added
backlog
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Oct 23, 2024
Just to update here, this issue will be addressed when merging #731 |
Able to reproduce, code snippet:
Will produce |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm trying to use the same Lambda-based Action Group for multiple Bedrock Agents. When I try that using the
.add_action_group()
method of theAgent
construct, I get the following error:I think this is due to a limitation of the CDK constructs and not the Bedrock service disallowing the same Action Group being used for multiple agents. Potentially it could be fixed by changing the construct ID
AgentLambdaInvocationPolicy
to include the construct ID of eachAgent
.Expected Behavior
I think same Lambda should be usable by multiple Agents.
Current Behavior
See first section.
Reproduction Steps
Create a Lambda-based Action Group and try to attach it to add it to two different agents via the
.add_action_group
method of theAgent
construct.Possible Solution
Use an identifier unique to the
Agent
construct when creating theAgentLambdaInvocationPolicy
ID.Additional Information/Context
No response
CDK CLI Version
2.162.1
Framework Version
0.1.271
Node.js Version
v20.11.0
OS
OSX
Language
Python
Language Version
No response
Region experiencing the issue
us-east-1
Code modification
No
Other information
No response
Service quota
The text was updated successfully, but these errors were encountered: