Skip to main content

AWS Detailed Billing Reports (DBR) (Legacy)

AWS Detailed Billing Reports (DBR) are a legacy AWS billing export format. Cloudaware still supports DBR ingestion for existing customer accounts, but for new integrations, using AWS CUR or AWS Data Exports (CUR 2.0) is recommended.

note

As of July 8, 2019, DBR is not available to new AWS customers. This guide applies only to existing environments that already rely on DBR. For new billing integrations, use:

How It Works​

  • AWS can generate Detailed Billing Reports and deliver them to an S3 bucket.
  • Cloudaware reads DBR files from S3 using the same cross‑account IAM role or IAM user configured for the main AWS integration.
  • Cloudaware then normalizes the data and makes it available in Cost Management dashboards. Because DBR uses an older schema, some billing dimensions and newer AWS billing features are available only in CUR or Billing Data Exports.

Prerequisites​

Before you begin, confirm that you have the following:

  • AWS payer account with access to Billing & Cost Management.
  • A dedicated S3 bucket for legacy DBR files.
  • AWS payer account is connected to Cloudaware. If it is not connected, complete the AWS Setup Guide first.
  • DBR already enabled in AWS.

Locate and Validate the DBR in AWS​

note

These steps reflect the legacy AWS console flow for DBR. UI labels and navigation may differ by account, and DBR options may no longer be visible in some environments.

  1. Sign in to the AWS console with billing permissions.
  2. Open Billing & Cost Management (for example, via My Billing Dashboard under your username).
  3. In the left navigation, open Billing preferences.
  4. Locate Detailed Billing Reports (Legacy) and confirm that DBR is enabled, if the option is still available.
  5. In the Save to S3 bucket section:
    • Select or configure the S3 bucket for DBR output.
    • Review and accept the generated S3 bucket policy.
  6. Select the desired report types, typically:
    • Monthly billing report
    • Cost allocation report
    • Detailed billing report with resources and tags
  7. Enable the cost allocation tags required for reporting:
    • Use Manage report tags to activate relevant billing tags.
  8. Save your billing preferences.

AWS then begins delivering DBR files to the configured S3 bucket according to its billing export schedule.

Grant Cloudaware Access to the DBR S3 Bucket​

Cloudaware uses the same IAM role or IAM user that it uses for AWS configuration ingestion. That principal must have permission to read the DBR files in S3.

  1. Confirm that the Cloudaware IAM role or user has:
    • s3:ListBucket on the bucket that stores DBR files
    • s3:GetObject on the DBR object prefixes
  2. If you are using a Cloudaware‑provided CloudFormation template for AWS onboarding:
    • Download the template from Admin → Amazon Web Services for the payer account.
    • Confirm that the DBR bucket name and any required prefix are included.
    • Update the CloudFormation stack in AWS with the revised template so that the IAM role includes access to the DBR bucket.
tip

If you change the DBR bucket or prefix, download and reapply the Cloudaware CloudFormation Template so the permissions remain aligned.

Enable AWS DBR Billing Integration in Cloudaware​

  1. In Cloudaware, go to Admin.
  2. Find AWS Billing and click CONFIGURED.
  3. Under Payer Account, locate the payer account entry or review the individual member accounts.
  4. Confirm that Cloudaware has discovered the correct billing report for the expected S3 bucket and prefix. The integration status must be green.
  5. In Cost Fields Handler, confirm the selected report type. Cloudaware uses the selected report type as the billing source for cost data on CMDB objects. For AWS DBR-based billing, DBR must be selected. If needed, click EDIT and select DBR. Click SAVE.
note

After billing is enabled, Cloudaware begins ingesting new DBR files during the next collection cycle.

Verification​

After you enable the integration, wait until the next collection cycle for data to appear.

  • In Cloudaware, go to Admin → AWS Billing → CONFIGURED. Confirm that the DBR integration status is green and DBR is selected in Cost Fields Handler.
  • Confirm that costs appear as expected for AWS objects in the Cloudaware CMDB.
  • In Cost Management dashboards:
    • Filter to AWS if needed and confirm that account IDs, services, regions, and cost allocation tags appear as expected.
    • Compare totals against the AWS Billing & Cost Management console for the same time ranges and scopes.

See also: AWS Billing Verification

Troubleshooting​

If costs do not appear within 24 hours, check the following:

  • Confirm that DBR files are being generated and arrive in the S3 bucket.
  • Verify that the Cloudaware IAM role or user has the required S3 permissions on the DBR bucket and object prefixes:
    • s3:ListBucket on the bucket
    • s3:GetObject on the prefix
  • In Cloudaware Admin → AWS Billing → CONFIGURED, check that the DBR billing source is discovered, enabled, and has green status, and that the report type in Cost Fields Handler is set to DBR.
  • Review any error or warning messages shown for the affected integration.
note

Data collection and processing time in Cloudaware depends on the volume of billing files.

See also: AWS Billing Troubleshooting

Security Notes​

  • Cloudaware uses a read‑only cross‑account IAM role or IAM user and never writes to your S3 buckets.
  • Restrict the role or user to the minimal required permissions on the DBR bucket and prefixes.
  • Use dedicated S3 buckets or prefixes for billing data if you require tighter access control and auditing.