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

AWS cost attribution (3/4): deploy to all other AWS clusters #4878

Closed
23 tasks done
Tracked by #4872
consideRatio opened this issue Sep 24, 2024 · 0 comments · Fixed by #5046
Closed
23 tasks done
Tracked by #4872

AWS cost attribution (3/4): deploy to all other AWS clusters #4878

consideRatio opened this issue Sep 24, 2024 · 0 comments · Fixed by #5046
Assignees

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Sep 24, 2024

Definition of done

Cost attribution system is deployed, or offered to be deployed in case we are blocked by community cloud permissions, to all AWS clusters according to the four steps in https://infrastructure.2i2c.org/howto/cost-attribution/aws/

2i2c AWS organization member accounts

  • 2i2c-aws-us
  • catalystproject-africa
  • gridsst
  • jupyter-health
  • kitware
  • nasa-cryo
  • opensci
  • smithsonian
  • strudel
  • ubc-eoas
  • victor

Standalone AWS accounts

  • nmfs-openscapes
  • openscapes

Community AWS organization's member accounts

@consideRatio consideRatio changed the title AWS cost attribution (4/n): roll out to all other communities AWS cost attribution (4/n): deploy to all other AWS clusters Sep 25, 2024
@consideRatio consideRatio changed the title AWS cost attribution (4/n): deploy to all other AWS clusters AWS cost attribution (3/n): deploy to all other AWS clusters Sep 25, 2024
@consideRatio consideRatio changed the title AWS cost attribution (3/n): deploy to all other AWS clusters AWS cost attribution (3/4): deploy to all other AWS clusters Sep 25, 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