A new AWS Account is healthy but showing as "No Current Billing" and its cost data is missing in the Cost History report.

Products

• CloudHealth

Issue/Introduction

This scenario is likely due to timing or there is a missing configuration step.     

These are the conditions: 

• Account Type shows as "No Current Billing"
• No data in Cost History report.
• Newly configured Consolidated Account is Healthy

When a newly Consolidated Account is configured, and its Account Type shows as "No Current Billing" and no cost data is being collected for it. This usually means that CloudHealth has not yet received any billing file for the account in question. This can happen if the account has not incurred any costs, or it has incurred costs, but the platform cannot access the Cost and Usage Reports (CURs) in the Billing Bucket.

Cause

1. CUR created for the AWS Account is misconfigured.
2. Often times the Policy added to the IAM Role in AWS console does not mention the correct S3 Billing Bucket Name, or it mentions the bucket, but the Bucket Name is not all lower case letters. 
   • This could happen when the entire policy is not copied. 
   • Or when a new CUR and a new billing bucket are created, but the policy statement is not updated of the role to allow the platform access to the new bucket. In this scenario, the role is trying to access the old bucket and needs to be updated. 

Note: S3 bucket name should be ALL LOWER CASE

Resolution

1. Ensure that you make the following entries and selections:
   
   • Check the box next to Include Resource ID.
   • Report path prefix: Enter a unique prefix.
   • Time granularity: Select Hourly.
   • Report versioning: Select Create new report version.
   • Compression: Select GZIP
   • Review Help Center documentation for more information: https://techdocs.broadcom.com/us/en/vmware-tanzu/cloudhealth/tanzu-cloudhealth/saas/tnz-cloudhealth/getting-started-with-tanzu-cloudhealth-aws-quick-start.html#configuring-aws-payer-account
2. The Solution is to navigate to Setup > Accounts > AWS and view the AWS account in question, click Generate Policy, select all and copy. The billing bucket name is included in the resulting policy towards the end as such. (Note: S3 bucket name should be ALL LOWER CASE).
   
   

Next, within the AWS Console, edit the IAM Policy associated with the selected account and paste the JSON policy copied from the CloudHealth platform.

Once the platform detects line items belonging to the account(s) in question (this generally takes place during overnight processing) the ‘Account Type’ status will be updated accordingly and data will start flowing into the CloudHealth platform.

 

Please review the following Knowledge Base articles that troubleshoot other scenarios where Account Type is "No Current Billing":

https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=282950

https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=284273