Managing S3 Bucket Data for AWS CUR and CloudHealth PGB (Partner Generated Billing)
search cancel

Managing S3 Bucket Data for AWS CUR and CloudHealth PGB (Partner Generated Billing)

book

Article ID: 282770

calendar_today

Updated On: 05-08-2024

Products

CloudHealth

Issue/Introduction

This KB article provides guidance on purging or cleaning up the S3 bucket where AWS CUR files stored for CloudHealth and recommendations for both CUR/DBR and Partner Generated Billing (PGB) buckets.

Environment

AWS

Resolution

CUR/DBR Billing Files

  • Current Month: Retain the current month's folder and files entirely, as they contain ongoing billing data.
    Previous Months: Ideally, keep the data for the previous two months to account for potential CUR collection issues.
    Older Months: You can safely remove data from months older than the past two without impacting cost data in CloudHealth.
  • Important Note:
    Do not delete the root manifest file within the CUR directory.
    Avoid editing or modifying the contents of the CUR folder or DBR files.

Partner Generated Billing (PGB) Bucket

  • CloudHealth utilizes an internal bucket for storing statements and billing data.
    The PGB bucket stores data written by CloudHealth during PGB processing.
    Partners can safely purge all content from the PGB bucket written by CloudHealth.
    Re-running PGB for a specific month will prompt CloudHealth to rewrite the data within the PGB bucket.
    While CloudHealth doesn't directly access data from the PGB bucket, it monitors the bucket for parity checks between its version and the partner's version.