Skip to main content

AWS Billing Verification

Use this guide to verify AWS‑specific billing integrations in Cloudaware, including Data Exports (CUR 2.0), CUR, and DBR (legacy).

  • Audience: Cloudaware administrators, FinOps teams
  • Outcome: Confirmed AWS billing data arrival, freshness, and alignment with AWS billing reports

AWS Data Exports (CUR 2.0)​

See also: AWS Billing Data Exports (CUR 2.0)

  1. Data export configuration.
    • In the AWS console, open Billing and Cost Management → Cost and Usage Analysis → Data reports.
    • Confirm that the CUR 2.0 Data Export used by Cloudaware is:
      • Active.
      • Configured for the correct time granularity and linked accounts.
      • Targeting the expected S3 bucket and prefix.
  2. S3 bucket contents.
    • In Amazon S3, open the bucket and prefix used for Data Exports.
    • Verify that new Parquet/CSV objects appear on the expected schedule.
    • Check object timestamps to confirm ongoing delivery.
  3. Integration status in Cloudaware.
    • In Cloudaware, go to Admin → AWS Billing.
    • Confirm that the Data Export‑based integration shows:
      • Status: green.
      • A recent Last update timestamp aligned with the export frequency.
  4. Cost consistency.
    • In Cloudaware Cost Management dashboards when provided, filter to:
      • Provider: AWS.
      • Scope and time range matching AWS Cost Explorer.
    • Compare total cost and major dimensions (accounts, services, regions) with AWS Cost Explorer using the same filters.

AWS Cost and Usage Reports (CUR v1)​

See also: AWS Cost & Usage Report (CUR)

  1. S3 CUR files.
    • In the AWS console, open Billing & Cost Management → Cost & Usage Reports.
    • Verify the CUR is Active and configured for the correct S3 bucket/prefix.
    • In S3, confirm:
      • New CUR objects are created regularly (for example, daily).
      • Object timestamps roughly match your billing export schedule.
  2. Integration status in Cloudaware.
    • In Cloudaware, go to Admin → AWS Billing.
    • Confirm that under Payer Account entries have green status.
  3. Cost consistency.
    • In Cloudaware Cost Management dashboards when provided, filter to:
      • Provider: AWS.
      • Time range: last full day or month.
    • Compare total unblended or amortized cost (depending on your view) with AWS Cost Explorer using the same filters.
  4. Account and tag coverage.
    • Verify that:
      • All expected management (payer) and member (linked) accounts appear in Cloudaware views.
      • Cost allocation tags you use in AWS are present as dimensions for grouping and filtering.

AWS DBR (Legacy)​

See also: AWS Detailed Billing Reports (DBR)

  1. DBR generation.
    • In the AWS console, open Billing & Cost Management → Billing preferences (or the legacy Detailed Billing Reports section).
    • Confirm that legacy Detailed Billing Reports are still enabled for the account and configured to deliver to the expected S3 bucket.
  2. S3 DBR files.
    • In Amazon S3, open the DBR bucket and prefix.
    • Verify that DBR files are created for recent billing periods (monthly and/or cost allocation reports).
  3. Integration status in Cloudaware.
    • In Cloudaware, go to Admin → AWS Billing.
    • Locate the DBR‑based billing entry (for legacy tenants it may appear as DBR Account or similar) and confirm:
      • Status: green.
      • Last update: recent.
  4. Cost checks.
    • In Cloudaware Cost Management dashboards when provided, filter to:
      • Provider: AWS.
    • Compare totals and key breakdowns (payer vs linked accounts, major services, tags) against the AWS Billing & Cost Management console for the same time range and scope.