You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see an option added that allows common tagging to resources created with bedrock-claude-chat.
Also, when creating each bot, would it be possible to add a setting that allows tagging of resources created for each bot?
Why the solution needed
For cost allocation using cost allocation tags and environment settings.
I have multiple workloads running within my AWS account and I need to clarify bedrock-claude-chat minutes.
Also, it is expected that the department responsible for costs will be different for each bot.
Additional context
Common tags are
・api-publish.ts
・bedrock-chat.ts
・bedrock-custom-bot.ts
to
cdk.Tags.of(app).add("string", "string");
It seems possible to do this by adding code like this.
Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?
Yes, I am able to implement the feature and create a pull request.
No, I am unable to implement the feature, but I am open to discussing the solution.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
I would like to see an option added that allows common tagging to resources created with bedrock-claude-chat.
Also, when creating each bot, would it be possible to add a setting that allows tagging of resources created for each bot?
Why the solution needed
For cost allocation using cost allocation tags and environment settings.
I have multiple workloads running within my AWS account and I need to clarify bedrock-claude-chat minutes.
Also, it is expected that the department responsible for costs will be different for each bot.
Additional context
Common tags are
・api-publish.ts
・bedrock-chat.ts
・bedrock-custom-bot.ts
to
It seems possible to do this by adding code like this.
Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?
The text was updated successfully, but these errors were encountered: