search

kubecost / cost-analyzer-helm-chart

Kubecost helm chart
http://kubecost.com/install
Apache License 2.0
465 stars 413 forks source link

AWS Cloud Integration “No Athena Bucket Configured” #1840

Closed thomasvn closed 10 months ago

thomasvn commented 1 year ago

Describe the bug

When setting up AWS Cloud Integration via the user interface, the UI displays “No Athena Bucket Configured” despite having properly set up the Cloud Integration.

However, when setting up AWS Cloud Integration via the Helm values, there are no errors.

To Reproduce

  1. Ensure you are starting with configs that are known to work (i.e. configs that have been tested via Helm values as well)
  2. Go to http://my.kubecost.com/settings
  3. Cloud Cost Settings -> External Cloud Cost Configuration (AWS) -> Update -> Enter your AWS Cloud Integration configs here
  4. Hit the following endpoint to start the CloudUsage pipeline: http://my.kubecost.com/model/etl/cloudUsage/rebuild?commit=true
  5. Hit the following endpoint to start the Reconciliation pipeline: http://my.kubecost.com/model/etl/asset/reconciliation/run?commit=true
  6. Verify that you can see out-of-cluster costs and adjustments in the “/assets” view.
  7. Go to http://my.kubecost.com/diagnostics and check whether the “No Athena Bucket configured” diagnostic is red

Expected behavior

The “No Athena Bucket configured” diagnostic should have a green check mark.

Screenshots

Screenshot verifying that my Cloud Integration was successfully set up:

Screenshot verifying that the CloudUsage and Reconciliation pipelines both successfully ran:

┆Issue is synchronized with this Jira Task by Unito

thomasvn commented 1 year ago

Additionally, here is a doc describing how to access my environment to test the issue.

Adam-Stack-PM commented 1 year ago

A note on this issue from a conversation with Ajay.

"Most people set this up via helm config, so I don't think this is p1 for 1.99, but it feels like we should commit to this for v1.100"

Pushing to v1.100.

github-actions[bot] commented 10 months ago

This issue has been marked as stale because it has been open for 360 days with no activity. Please remove the stale label or comment or this issue will be closed in 5 days.

github-actions[bot] commented 10 months ago

This issue was closed because it has been inactive for 365 days with no activity.