Correcting Missing Month-End Cost Data Caused by AWS CUR Assembly ID Mismatches

Products

• CloudHealth

Issue/Introduction

CloudHealth users may occasionally notice missing or partial cost data for the final day of a billing cycle. This can occur when AWS generates multiple versions of a Cost and Usage Report (CUR) in rapid succession with different Assembly IDs.

If AWS delivers a report with an older Assembly ID after a newer version has already been processed, the root manifest file in the S3 bucket may point to an outdated data set. Because CloudHealth relies on the root manifest to trigger updates, the platform will not automatically ingest the most recent data if the manifest remains pointed at an older version that has already been collected.

Resolution

To resolve this and ensure CloudHealth collects the most accurate data, the root manifest file must be updated to point to the correct Assembly ID.

Since CloudHealth operates with read-only access to your S3 billing buckets, you must work with AWS Support or your internal DevOps team to perform the following steps:

1. Identify the Latest Version: In your S3 bucket, locate the sub-folder corresponding to the most recent Assembly ID (based on the timestamp or contents) for the affected month.

2. Locate the Source Manifest: Find the manifest file within that specific Assembly ID sub-folder (this is the Source Object Key).

3. Update the Root Manifest: Copy that manifest file to the Root Location of the CUR (the Target Object Key), effectively overwriting the existing root manifest so it points to the newest data.

4. Verification: Once the root manifest is updated, CloudHealth will detect the change during its next scheduled collection cycle and automatically backfill the missing costs.

Note: If this occurs frequently, we recommend opening a ticket with AWS Support to inquire why older report versions are being delivered out of sequence, as this disrupts automated billing workflows.