Skip to content

[Feature Request]Cost allocation tag settings #659

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

Closed
1 of 2 tasks
HirokiNakatani opened this issue Dec 21, 2024 · 4 comments
Closed
1 of 2 tasks

[Feature Request]Cost allocation tag settings #659

HirokiNakatani opened this issue Dec 21, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@HirokiNakatani
Copy link

HirokiNakatani commented Dec 21, 2024

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

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.
@statefb
Copy link
Contributor

statefb commented Jan 15, 2025

Could you check if following admin feature work?
https://github.com/aws-samples/bedrock-claude-chat/blob/v2/docs/ADMINISTRATOR.md

@statefb statefb added needs-info Need more information such as reproduction step and removed needs-triage labels Jan 15, 2025
@HirokiNakatani
Copy link
Author

The above has been confirmed. However, it seemed impossible to check AWS resources other than bots. Is it possible to visualize it using cost allocation tags?

@github-actions github-actions bot added the stale Issue labeled as stale will be closed automatically label Feb 17, 2025
Copy link
Contributor

This issue has been labeled as "stale" due to no response by the reporter within 1 month (and 14 days after last commented by someone). And it will be closed automatically 14 days later if not responded.

@statefb statefb added enhancement New feature or request and removed stale Issue labeled as stale will be closed automatically needs-info Need more information such as reproduction step labels Feb 17, 2025
@statefb
Copy link
Contributor

statefb commented Mar 21, 2025

Added multi env support with tagging.

@statefb statefb closed this as completed Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants