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
The AWS cost attribution system is a simple Python webserver accessing AWS Cost Explorer API to summarize information about an AWS accounts billing data. This summarized billing data is then exposed via a k8s Service, making a Grafana instance able to access it as a datasource. There is a datasource plugin used for this in Grafana called Infinity, as it helps parse the JSON response provided by the webserver. The openscapes grafana instance currently has this system deployed, and the Grafana instance has a Dashboard defined within it that we can re-use.
Kinds of work involved
Most of the AWS specific parts have been done, so now working this epic will mostly involve less cloud specific parts, such as:
terraform / eksctl
grafana dashboard development like in jupyterhub/grafana-dashboards
interaction and communication with openscapes and nasa-cryo community
This EPIC captures the AWS part of #4384:
Quick intro
The AWS cost attribution system is a simple Python webserver accessing AWS Cost Explorer API to summarize information about an AWS accounts billing data. This summarized billing data is then exposed via a k8s Service, making a Grafana instance able to access it as a datasource. There is a datasource plugin used for this in Grafana called Infinity, as it helps parse the JSON response provided by the webserver. The openscapes grafana instance currently has this system deployed, and the Grafana instance has a Dashboard defined within it that we can re-use.
Kinds of work involved
Most of the AWS specific parts have been done, so now working this epic will mostly involve less cloud specific parts, such as:
As seen in openscapes
You can inspect the dashboard live at https://grafana.openscapes.2i2c.cloud/d/b4dbba938e548f10/cloud-cost-attribution?orgId=1
Tasks
The text was updated successfully, but these errors were encountered: