Configuring CUR Exports for AWS Billing transfer via DataConnect

Products

• CloudHealth

Issue/Introduction

When onboarding new accounts through DataConnect for AWS Billing transfer, customer may experience missing usage data or integration failures.

Resolution

To ensure full visibility and successful integration, follow these configuration requirements when setting up your AWS Cost and Usage Report  for AWS Billing transfer via DataConnect 

1. Detailed Line-Item Visibility:

For DataConnect to accurately track and display usage, the CUR export generated at the AWS Master (Payer) level must be configured to capture granular data for all sub-accounts.

Action: Verify that the CUR includes all account IDs intended for DataConnect onboarding.

Requirement: The generated files must explicitly capture and display detailed line-item data associated with the DataConnect account IDs. This ensures that the integration can "see" and attribute costs to the correct managed accounts.

2. Select the Correct Export Format (Legacy CUR)
AWS recently introduced CUR 2.0, which utilizes a different schema and delivery structure. CloudHealth does not support CUR 2.0 at this time.

Action: When creating a new CUR in the AWS Billing & Cost Management console, do not select the default CUR 2.0 option.

Requirement: You must explicitly select the Legacy CUR Export option.

[!IMPORTANT]
Failure to use the Legacy CUR format will result in processing errors within the CloudHealth platform, as the system will be unable to parse the new 2.0 data structure.

3. Step-by-Step Configuration

1. Log in to the AWS Console, navigate to your profile, and click Account.
2. From the left menu, select Cost & Usage Reports and click Create Report.
3. Configure the report with the following specific settings:
• Report Name: Use an identifiable name (e.g., cloudhealth-hourly-cur).
• Resource IDs: Check the box to Include Resource ID.
• Data Refresh: Enable Automatically refresh your Cost & Usage Report for closed billing months.
• Time Granularity: Select Hourly.
• Report Versioning: Select Create a new report version.
• Compression: Select GZIP.
4. S3 Bucket: Configure a unique S3 bucket and region, ensuring you accept the generated default policy.
5. Review your settings and click Create Report.

Please find below document for reference:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/cloudhealth/saas/index/working-with-partner-platform-of-tanzu-cloudhealth-working-with-partner-platform/working-with-partner-platform-of-tanzu-cloudhealth-aws-managed-service-providers.html#concept_1_create_cur_in_aws_console