Skip to main content

AWS Cost Explorer

Enable AWS Cost Explorer integration in Cloudaware to centralize visibility into AWS usage, costs, and spending trends. With this integration, Cost Explorer data becomes available alongside other billing sources in Cloudaware, helping FinOps and finance teams track budgets, identify anomalies, and optimize AWS spend.

  • Audience: Cloudaware administrators, FinOps, finance teams
  • Outcome: AWS Cost Explorer connected to Cloudaware so that AWS cost and usage analytics can be viewed and reported together with other billing data

Prerequisites

Before you begin, confirm that you have the following:

  • AWS Cost Explorer is enabled for your AWS payer (management) account. Refer to AWS Cost Explorer documentation for enablement steps.
  • The AWS payer account is already connected to Cloudaware. If it is not connected, complete the AWS Setup Guide first.

Enable AWS Cost Explorer in Cloudaware

note

Enabling AWS Cost Explorer and allowing Cloudaware to read Cost Explorer data may incur additional AWS charges. For details, refer to AWS Cost Explorer API pricing.

  1. In Cloudaware, go to Admin.
  2. Under Billing integrations, find AWS Cost Explorer and click + ADD.
  3. Select the AWS payer account that has AWS Cost Explorer enabled.
  4. Click SAVE.

Verification

  • In Cloudaware, go to AdminAWS Cost ExplorerCONFIGURED:
    • Confirm that the integration status is green.
  • In Cost Management dashboards:
    • Confirm that AWS cost trends and breakdowns (accounts, services, regions) align with what you see in AWS Cost Explorer for the same scope and period.

Troubleshooting

If AWS Cost Explorer data does not appear as expected in Cloudaware:

  1. Verify AWS Cost Explorer on the payer account.

    • Confirm that AWS Cost Explorer is still enabled for the payer account.
    • Check for any billing, account, or access issues in AWS that could affect Cost Explorer data.
  2. Review the Cost Explorer integration in Cloudaware. Go to AdminAWS Cost Explorer and verify that:

    • The correct payer account is selected.
    • No warnings or errors are shown for the integration.
  3. Validate the AWS account integration and permissions.

    • In Cloudaware, go to AdminAmazon Web Services, then click CONFIGURED. Confirm that the payer account integration is healthy.
    • Make sure the required permissions or IAM roles for Cost Explorer API access are still present and have not been removed or restricted.

If the integration status remains red or data continues to lag significantly, contact support@cloudaware.com with:

  • Your Cloudaware org name.
  • The affected payer account ID.
  • Screenshots from AWS Cost Explorer and the Cloudaware AWS Cost Explorer integration screen.