Billing Transfer CUR not available as “AWS Cost & Usage” data source in FlexReports

Products

• CloudHealth

Issue/Introduction

When using AWS Billing Transfer, CloudHealth ingests the CUR and standard reports (such as Cost History) show data correctly, but in FlexReports the only selectable data source is “AWS Cost History” instead of “AWS Cost & Usage”​.​

Environment

• CloudHealth FlexReports.​

• AWS accounts configured with the AWS Billing Transfer feature and generating Billing Transfer CURs.

Cause

AWS Billing Transfer can produce CUR files where multiple payer-related account identifiers (for example, multiple PayerAccount IDs) appear in a single file or partition. CloudHealth can use these CURs for standard reporting, but FlexReports does not currently expose them as an “AWS Cost & Usage” data source when this structure is present.

Resolution

There is no CloudHealth-side configuration change that enables “AWS Cost & Usage” as a FlexReports data source for Billing Transfer CURs today. Customers should:​

• Continue using standard reports (such as Cost History) for Billing Transfer cost visibility.​​

• Work with AWS Support to review the structure of the Billing Transfer CUR, especially where multiple payer account identifiers appear in the same CUR file or partition.​

• Coordinate with their CloudHealth TAM to monitor product updates related to Billing Transfer and FlexReports behavior.