The CloudHealth platform is experiencing an issue where AWS accounts may unexpectedly report a 'No Current Billing' 'Account Type' state even though the Account is configured correctly with valid credentials.
You may also see a warning banner advising -
"We've detected that you do not have an AWS Cost and Usage report (CUR) configured for these accounts: . CloudHealth is no longer reporting on costs for these accounts. To resume cost reporting for these accounts, complete the configuration or contact your CloudHealth Administrator."
This is a known issue that is actively being worked on by our engineering team and it does not impact the collection of AWS data.
One side effect of this issue is that RI Recommendation tools may not operate as intended while accounts are in this state as they may not be evaluating on a full set of accounts.
If you experience this issue where your accounts are configured correctly with a 'Heathy' status but you observe a 'No Current Billing' 'Account Type' state please reach out to email@example.com
to have a manual workaround applied.
We will provide further updates once a full fix is in place.
Oct 10, 23:36 EDT