Skip to content
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

Enable cost allocation tags on openscapes AWS account #4473

Closed
Tracked by #4453
yuvipanda opened this issue Jul 22, 2024 · 2 comments · Fixed by #4529
Closed
Tracked by #4453

Enable cost allocation tags on openscapes AWS account #4473

yuvipanda opened this issue Jul 22, 2024 · 2 comments · Fixed by #4529
Assignees

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Jul 22, 2024

Once #4464, #4485 and #4482 are done, we need to 'enable' using the various tags we have set up as a 'cost allocation tag'.

This will need to be done via terraform: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ce_cost_allocation_tag.

The following tags would need to be 'activated':

  • 2i2c:hub-name
  • 2i2c:node-purpose
  • aws:eks:cluster-name (autogenerated by AWS)
  • kubernetes.io/created-for/pvc/name (allows us to track cost of hub db PVC and prometheus PVC)
  • kubernetes.io/created-for/pvc/namespace (same as above)
  • kubernetes.io/cluster/openscapeshub (enables us to track disks used by PVCs)

Definition of done

Looking at https://us-east-1.console.aws.amazon.com/billing/home#/tags after logging into the openscapes account should show these tags being activated

@yuvipanda yuvipanda changed the title Enable cost allocation tags on openscapes account for EFS Enable cost allocation tags on openscapes AWS account Jul 24, 2024
@consideRatio
Copy link
Contributor

(This issue turned out to not be blocked by #4464)

@consideRatio consideRatio self-assigned this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants