This FAQ provides answers to some of the common questions about our application.

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

A: CloudCheckr collects your AWS data using multiple collectors such as S3, Detailed Billing Report, CloudTrail, AWS Config, and the AWS API. Here are the typical time-frames for each:

  • S3 - The time to collect your S3 data is dependent on the number of S3 objects you are storing within AWS. On average, CloudCheckr collects 250 million objects per day. By default we run your S3 updates once every 7 days.
  • Detailed Billing Report - CloudCheckr collects your Detailed Billing Report starting with the most recent month first, and working backwards for as many months as Detailed Billing Reports exist. This allows you to see your most recent costs information while CloudCheckr gathers all available data. Current month billing data is typically available to view within 10-15 minutes for small AWS accounts, with ALL months being available within an hour. For larger AWS accounts, the initial collection could take up to 24 hours. In the normal lifecycle of an account, AWS updates the DBR about once every 6 hours. CloudCheckr will continually scan for new billing data and will perform an update as soon as new data is found, resulting in a typical update cycle for a small-to-mid sized account of around four updates per day.
  • CloudWatch - CloudCheckr collects your CloudWatch data once a day. How long this job takes to run is dependent on the size of your CloudTrail logs.
  • CloudTrail/Config - CloudCheckr collects your CloudTrail/AWS Config files every hour.
  • AWS API - CloudCheckr collects a complete inventory of your resources and settings every 24 hours. The time to collect this data is entirely dependent on the size of your AWS deployment. Smaller AWS accounts will have their data available within 30 minutes, with most larger accounts taking 1-2 hours but possibly up to 24 hours. CloudCheckr will send a Summary email of its findings once your data is available.

Q: I entered the AWS credentials for my AWS master account, but I do not see any resource information for any of my sub-accounts.

A: When adding the credentials of a master payer account, CloudCheckr is able to show 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 payers. If you would like CloudCheckr to report on the payee accounts you will need to register IAM credentials for each separate payee account.

Q: My billing related emails (such as Daily Billing Summary) , did not trigger on the last day of the month, why?

A: In preparation for invoicing their customers AWS stops writing updates to the Detailed Billing Report on the last day of the month. As a result of this there is incomplete data for the last day and CloudCheckr will not trigger the billing related email. If we were to trigger that email it would contain imcomplete data for that day. Once AWS closes the month they will write the remaining hours for the last day of the month. At this time CloudCheckr will see that the month is closed and automatically reload the Detailed Billing Report. As part of finalizing the month CloudCheckr will then trigger the billing related emails for the end of the month.

Q: What is the difference between CloudWatch billing data and the Detailed Billing Reports?

A: CloudWatch has far more limited data, only providing a net bill for the month, and arrives in a 'lumpy' fashion (often it is not reported on a regular schedule). The Detailed Billing Report is written into 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 the use of Detailed Billing.

Q: Why is there no info displaying for the AWS bill on my dashboard?

A: Either Detailed Billing reports or CloudWatch Bill Monitoring must be enabled on your AWS account for CloudCheckr to retrieve your billing information. For instructions on enabling these features within AWS, review the topic, Preparing Your AWS Account.

Q: How do I delete an unwanted account?

A: Login to your CloudCheckr account which directs you to your Accounts page. Locate the account you would like to remove, and select the X in the column adjacent to the account name (labeled Actions). Confirm your deletion request.

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

Q: Will using CloudCheckr cause me to incur any additional charges from Amazon Web Services?

A: Amazon does charge a very small fee per API call (which we use to access your account). Example: If you have 1 million S3 objects, Amazon will charge you approximately $0.05 for CloudCheckr to inventory those files. 1 billion S3 objects would be $5.00.

Q: How do I change my password?

A: You can change your password at any time by choosing the Settings menu at the top of the page.

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

A: 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 topic, User Management.

If you have any questions or need assistance with adding users, please please use the CONTACT SUPPORT button at the top of this page to get in touch.

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

A: All of your accounts will be listed on the Accounts page. Once you have opened an account, you can view and access your other accounts by using the drop down in the top left menu.

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

A: Yes! You can have CloudCheckr import your Trusted Advisor checks into your CloudCheckr account. This will create a new tab in the Best Practices report labeled "Trusted Advisor".

You will need to given access for Trusted Advisor to CloudCheckr for this information to show up in the Best Practice report. To provide access to Trusted Advisor you must grant 'support:*', permissions to the IAM user used for CloudCheckr. Please contact support@cloudcheckr.com with any questions about this.

Q: Can CloudCheckr report on AWS GovCloud?

A: CloudCheckr is compatible with AWS GovCloud. However, if you have a GovCloud account and would like to use CloudCheckr, please send an email to support@cloudcheckr.com with your account information prior to adding your GovCloud credentials.

How did we do?