Number of AWS Bill Transfer data connects required to onboard the data at cloudhealth end for multi-tiered accounts

Products

• CloudHealth

Issue/Introduction

When onboarding complex multi-account AWS environments—specifically those utilizing AWS Billing Transfer or multi-tiered Cost and Usage Reports (CUR)—customers often face questions regarding how many DataConnect integrations need to be created in CloudHealth and how to ensure proper line-item visibility.

Cause

1>Once AWS has completed the Billing transfer the accounts should be available under Billing and Cost Management>Billing Transfer :

2> How many dataconnects should be created to onboard the data at cloudhealth end?

At CloudHealth end, the number of Data Connects you need to create directly mirrors how you are aggregating your AWS Billing data.
As we can see in the screenshot attached above there are two accounts  available under Billing and Cost Management>Billing Transfer.
Hence we need to create two dataconnects to onboard the data at cloudhealth end.

Resolution

DataConnect creation does not depend on account role classifications (such as whether an account is labeled as a Bill Receiver, Indirect Bill Source, or Direct Bill Transfer).The configuration depends directly on how billing data is aggregated within your AWS setup.

Step 1: Identify DataConnect Requirements Based on Aggregation

• Review your setup under AWS Billing and Cost Management > Billing Transfer.

• Count the total number of primary accounts holding direct transfer connections.

• Create a matching number of DataConnects in CloudHealth corresponding to each aggregated billing account.

Step 2: Validate CUR Export Contents

• Ensure that the Cost and Usage Report (CUR) generated on the AWS side explicitly includes the DataConnect accounts you are attempting to onboard.

• Verify that generated CUR files explicitly capture and display the detailed line-item data associated with the relevant DataConnect Account IDs within the new export.

Step 3: Confirm Visibility in CloudHealth

• Completing these steps ensures full visibility, accurate cost allocation, and proper tracking of all usage linked to the accounts managed through the DataConnect integration.