The JupyterHub Cost Monitoring system consists of the jupyterhub
Checkout the topic guide for more information on the system.
Steps¶
1. Enable cost monitoring system¶
The cost monitoring system requires a service account with the IAM permissions to read billing data from AWS Cost Explorer API. This is unconditionally enabled with the terraform variable enable_jupyterhub_cost_monitoring that sets up an IAM role, IAM policy and Kubernetes service account annotation.
See terraform/aws/variables.tf and terraform/aws/cost-monitoring.tf for the configuration.
2. Activate cost allocation tags¶
We can activate cost allocation tags for AWS accounts that we have billing permissions for (either through the 2i2c SSO or a standalone account), but not for AWS accounts that are managed by a community where we do not have billing permissions.
AWS accounts managed by the 2i2c SSO have cost allocation tags already enabled with the overarching billing account. Cost tags only need to be activated once per AWS organization.
See the topic guide for more information on which cost allocation tags are activated.
Explicitly activate the cost allocation tags by setting
enable_jupyterhub_cost_tags = truein the terraform/aws/projects/<cluster_name>.tf file.
If the apply operation fails with the following errors:
Tag keys not found
While it sounds like cloud resources haven’t been tagged, its probably because the billing system hasn’t yet detected them. It runs a few times a day, so you may need to wait a few hours for the billing system to have detected each tag at least once.
Linked account doesn’t have access to cost allocation tags.
This means we do not have billing permissions on the AWS account and is likely managed by a community (see Community-managed account).
We require a community member with the relevant billing permissions to enable the cost allocation tags on our behalf.
Below is a template message you can send to the technical contact. Note that <$CLUSTER_NAME> should be updated to the community’s cluster name.
In order for 2i2c to enable the cloud cost monitoring feature for your community, the following changes needs to be made in the AWS organization’s management account:
Declare that linked member accounts are allowed to access Cost Explorer.
This can be done via “Billing and Cost Management” -> “Cost Management Preferences”, where the checkbox “Linked account access” should be checked.
Enable a specific set of cost allocation tags.
This can be done via “Billing and Cost Management” -> “Cost Allocation Tags”.
The tags that to be activated are:
2i2c:hub-name
2i2c.org/cluster-name
2i2c.org/node-purpose
2i2c.org/volume-purpose
alpha.eksctl.io/cluster-name
kubernetes.io/cluster/<$CLUSTER_NAME>
kubernetes.io/created-for/pvc/name
kubernetes.io/created-for/pvc/namespace
3. (optional) Backfill billing data¶
You can optionally backfill billing data to tags having been around for a while but not enabled as cost allocation tags.
You can request this to be done once a day, and it takes a several hours to process the request. Make a request through the AWS web console by navigating to “Cost allocation tags” under “Billing and Cost Management”, then from there click the “Backfill tags” button.
4. Install jupyterhub-cost-monitoring Helm chart¶
The helm deployment is unconditionally enabled with jsonnet, unless explicitly overridden in the config/clusters/<cluster_name>/support.values.yaml file, and the configuration is automatically defined in the helm-charts/support/values.jsonnet file.
You can manually deploy the support chart with:
deployer deploy-support $CLUSTER_NAMETroubleshooting¶
If you don’t see data in the cost monitoring dashboard, you may want to look to
ensure the jupyterhub-cost-monitoring deployment’s pod is running in the support namespace, or if it reports errors in its logs.