Skip to main content

AWS Billing Troubleshooting

Use this guide to diagnose common issues with AWS billing integrations in Cloudaware, including CUR v1, Data Exports (CUR 2.0), and legacy DBR.

  • Audience: Cloudaware administrators, FinOps teams
  • Outcome: Identify and resolve missing or delayed AWS billing data, permission issues, and configuration mismatches.

Data Exports (CUR 2.0) Issues​

See also: AWS Billing Data Exports (CUR 2.0)

  • In the AWS console:
    • Open Billing and Cost Management → Cost and Usage Analysis → Data reports.
    • Confirm the Data Export is Active and targeting the expected S3 bucket and prefix.
  • In Amazon S3:
    • Verify that Data Export objects are appearing under the configured prefix.
    • Check for gaps in timestamps that may indicate export failures.
  • In Cloudaware:
    • Go to Admin → AWS Billing and confirm the Data Export integration is enabled and green.

Cost and Usage Reports (CUR v1) Issues​

CUR Files Not Found or Not Updated​

See also: AWS CUR

  • In the AWS console:
    • Go to Billing & Cost Management → Cost & Usage Reports and verify the report is Active.
    • Confirm Include resource IDs is enabled.
    • If available, ensure Automatically refresh your Cost & Usage Report when charges are detected for previous months with closed bills is enabled.
  • In Amazon S3:
    • Confirm CUR files are being written to the expected bucket and prefix.
    • Check object timestamps to confirm daily/hourly updates.

Cloudaware Cannot Read CUR Files​

  • In Cloudaware:
    • Go to Admin → AWS Billing and check whether the CUR source is discovered and status is green.
  • In AWS:
    • Verify the CloudFormation stack used by Cloudaware is up to date and references:
      • Correct CUR bucket name.
      • Correct CUR prefix (folder).
    • Confirm the cross‑account role has:
      • s3:ListBucket on the CUR bucket.
      • s3:GetObject on the CUR bucket prefix.
  • If you recently changed the CUR bucket or prefix:

AWS Organizations vs Member Accounts​

  • If you use a management account level CUR:
    • Ensure the AWS management (payer) account is onboarded to Cloudaware and the CUR includes all member accounts.
  • If you use member account level CURs only:
    • Verify each member account has its own CUR configured and Cloudaware CloudFormation stack updated with the correct bucket and prefix.
    • Confirm each member account CUR integration has green status in Cloudaware Admin → AWS Billing.

DBR (Legacy) Issues​

See also: AWS Detailed Billing Reports (DBR) (Legacy).

  • In the AWS console:
    • Confirm that legacy Detailed Billing Reports (DBR) are still enabled in Billing preferences (legacy section).
    • Verify the S3 bucket for DBR delivery is correct.
  • In Amazon S3:
    • Check that DBR files are present for recent months and that new files arrive as expected.
  • In Cloudaware:
    • Verify the DBR integration in Admin → AWS Billing is green.
    • If red, confirm:
      • The IAM role/user has s3:ListBucket and s3:GetObject on the DBR bucket/prefix.
      • Bucket name and prefix match the settings in the DBR template and Cloudaware configuration.

When to Contact Cloudaware Support​

If you have verified AWS exports, S3 permissions, and Cloudaware configuration but issues persist:

  • Collect the following before opening a ticket:
    • Cloudaware org name and affected AWS billing integration(s).
    • AWS payer and member account IDs in scope.
    • Screenshots or samples showing:
      • CUR/Data Export/DBR configuration in the AWS console.
      • S3 buckets and prefixes with recent objects.
      • AWS Billing integration status and any error messages in the Cloudaware UI.
  • Contact Cloudaware Support via your usual channel or support@cloudaware.com and include the collected information for faster triage.
On this page