AWS: General

These Frequently Asked Questions (FAQs) answer the most common questions we get asked about the relationship between CloudCheckr and AWS.

Question: How long does it take for CloudCheckr to collect my AWS data?


CloudCheckr collects AWS data from various sources including S3 buckets, the Detailed Billing Report (DBR), CloudTrail, AWS Config, and the AWS API.

The timeframe for data collection varies for each of these sources and services.


Time Frame


  • Depends on the number of S3 objects you are storing within AWS
  • By default, CloudCheckr collects 1 million objects daily
    If you are looking for total object limits, refer to the Summary or List of S3 Buckets pages (Inventory > S3 > Summary and Inventory > S3 > List of S3 Buckets).

    If the system hits the S3 object limit, you may only see a subset of the data. If you need the S3 Top 10 metadata, contact Support to increase your limit.

    CloudCheckr only provides this increase on an individual acccount basis.
  • By default, CloudCheckr runs your S3 updates once every 7 days


  • CloudCheckr starts with the most recent month and works back to the first month it was generated
  • Allows you to see your most recent costs information while CloudCheckr gathers all available data
  • Smaller accounts: billing data for current month is available within 10-15 minutes while billing data for all months is available within an hour
  • Larger AWS accounts: initial collection may take up to 24 hours
  • In the normal account life cycle:
    • AWS updates the DBR once every 6 hours
    • CloudCheckr will continually scan for new billing data and will perform an update when it finds new data, which for small- and mid-sized accounts is approximately 4 times daily


  • CloudCheckr collects your CloudWatch data every six hours but it can collect up to 4 times a day


  • CloudCheckr collects your CloudTrail/AWS Config files every hour


  • CloudCheckr collects a complete inventory of your resources and settings every 24 hours
  • Time frame depends on the size of your AWS deployment:
    • Smaller AWS accounts: 30 minutes
    • Larger accounts: 1-2 hours but may take up to 24 hours
  • CloudCheckr will send a Summary email when your data is available

Question: Why don't I see resources for my payee accounts if I provided my AWS master account credentials?


When adding the credentials of a master payer account, CloudCheckr shows complete cost data across the entire Consolidated Billing Family. However, AWS does not provide any Inventory, CloudWatch, or CloudTrail data for payee accounts within the payer accounts. If you want CloudCheckr to report on payee accounts, you must apply IAM credentials to each payee account.


As part of their invoice preparation, AWS stops writing updates to the DBR on the last day of the month. As a result, CloudCheckr will not trigger any billing-related emails because the billing data will be incomplete for that day. Once AWS closes the month, they will write the remaining hours for the last day of the month. CloudCheckr will see that the month is closed and automatically reload the DBR. Once the month's billing is finalized, CloudCheckr will trigger the billing-related emails.

Question: What is the difference between CloudWatch billing data and the DBR?


CloudWatch has more limited data. AWS only provides a net bill for the month, and often, does not report it on a regular schedule. AWS writes the DBR to the master account's S3 bucket. It contains all cost information, including credits, has greater consistency, and allows for greater analysis with full tags, timing, grouping, and other relevant details. For this reason, we strongly recommend using the DBR.

Question: Why doesn't the dashboard display my AWS billing information?


You must enable the DBR or the CloudWatch Bill Monitoring in your AWS account so that CloudCheckr can retrieve your billing information. For instructions on how to enable these features, review the Preparing Your AWS Account topic.

Question: How do I delete a CloudCheckr account I no longer need?


Log in to CloudCheckr and from the account list, locate the account you would like to delete. In the Actions column, select the icon and confirm your deletion request.

This action is not reversible. All data in the selected account will be permanently deleted.

Question: Will I incur additional charges from AWS if I use CloudCheckr?


AWS does charge a very small fee per API call, which CloudCheckr uses to access your AWS account. For example, if you have 1 million S3 objects, AWS will charge you approximately $0.05 for CloudCheckr to inventory those files. For 1 billion S3 objects, AWS would charge you approximately $5.00.

Question: How do I change my password?


From the menu bar in CloudCheckr, click the Settings icon and select User > Change Password. On the User Settings screen, type and confirm your new password and click Save Settings.

Question: Can I give others access to my CloudCheckr account?


CloudCheckr customers can self-provision and manage access to their account. You can limit which accounts users can access, and whether they can view CloudCheckr's cost reports. You can also determine whether the users will be able to view Blended or Unblended costs within each cost report. For more information, review the User Management topic.

If you have any questions or need assistance with adding users, please contact our Support team.

Question: How can I view a complete list of my available accounts?


CloudCheckr displays all of your accounts on the Accounts page. Click an account from the list to view the reports and data associated with that account. To select another account, go to the left navigation pane and click Back to List of Accounts to return to the Accounts page.

Question: Can I view my Trusted Advisor checks within CloudCheckr?


Yes! You can enable CloudCheckr to import your AWS Trusted Advisor checks into your CloudCheckr account. To ensure that the AWS Trusted User checks are are part of your Best Practices report, you must first grant 'support:*' permissions to your IAM user in CloudCheckr. This action will create a Trusted Advisor tab in your Best Practices report. Please contact our Support team if you need additional help.

Question: Can CloudCheckr report on AWS GovCloud?


CloudCheckr is compatible with AWS GovCloud. However, if you have a GovCloud account and would like to use CloudCheckr, please contact our Support team.

Question: What are the reasons why CloudCheckr shows different costs than AWS Cost Explorer?


Here are the main reasons:
  • CloudCheckr offers a list cost rate in addition to unblended and blended cost rates.
  • AWS Cost Explorer and CloudCheckr amortize RIs differently.
  • CloudCheckr provides RI unsharing and AWS Cost Explorer does not.
  • The transition from the Detailed Billing Report (DBR) to the Cost and Usage Report (CUR) drives changes in the line item values between these cost reports.
  • AWS Cost Explorer and CloudCheckr apply credits differently.
  • AWS Cost Explorer and CloudCheckr calculate AWS Marketplace charges differently.
For more information, review the Cost and Billing FAQ topic.

Question: Does CloudCheckr use the DBR or the CUR? If so, how does this impact me?


At this time, CloudCheckr allows its customers to use the DBR or the CUR, but recommends that existing customers enable the CUR as soon as possible since AWS plans to deprecate this method by the end of 2019. If you are new customer, our Customer Service Managers will help you set up the CUR during your onboarding.

For more information, review the Transition from DBR to CUR FAQ topic.

How did we do?