Onboarding FAQ

Question: How is my CloudCheckr Invoice Calculated?


Your CloudCheckr Invoice is calculated off of your previous month’s spend.

Question: Why does my invoice change month over month?


As your spend increases/decreases, so will your CloudCheckr Invoice.

Question: Can I submit a Feature Request?


Yes! We always encourage our customers to submit enhancement requests. If you have a request that you think could enhance the product, we ask that you work with your Account Owner/Account Manager to discuss the request, and they will work with our Product Team to get this officially submitted.

Question: What is the ticket/bug resolution process?


If you are experiencing an issue with our application, we ask that you submit a ticket through our portal: https://cloudcheckr.atlassian.net/servicedesk .

You can also access this by clicking on from any page within the application. Our team of Support Engineers will work through the issue and attempt to reproduce the problem. If the issue is something that can be solved with the Support Engineer, they will work with you to correct the issue. If the issue requires a potential escalation to get resolved (such as a potential bug), the Support Engineer will escalate as appropriate and will provide you with updates as they are available.

Question: What is the difference between a bug and a feature request?


A bug is a fundamental issue in the product that is an unexpected behavior, whereas a feature request enhances the product.

Example Bug: “I am attempting to load a specific page within CloudCheckr that has always worked and it is displaying ‘Sorry, there was an error please contact Support to resolve’ when trying to access it today.”

Example Feature Request: “I would like to be able to export the Audit History section as an Administrator of CloudCheckr. Why am I not able to do this?”

Question: How does my cost data get processed in CloudCheckr?


All AWS cost data is ingested into CloudCheckr from the Detailed Billing Report (DBR) as well as the Cost and Usage Report (CUR). See the following articles for configuration guides:

Article for Enabling DBR within AWS

Article for Enabling the CUR within AWS

Article for Enabling the CUR within CloudCheckr

Question: How do Inventory, Best Practice Checks, Security, and Utilization get processed/updated?


These CloudCheckr modules get picked up through our Discovery process, a background job which is updated once a day by default. You do have the ability to manually kick this job off by navigating to the notification bubble (top right of the application) and clicking on ‘Update’ under the ‘Reports Updated’ section.

Question: What can I do with the API?


You can access the same data as within our UI, but with the enhancement of the access being programmatic. This can help you or your admins created streamlined processes. For a general guide, see: https://success.cloudcheckr.com/article/gbnfxmoyo6-api-user-guide

Question: Why does CloudCheckr cost look different then AWS Cost Explorer?


CloudCheckr is currently using the legacy AWS Detailed Billing Report (DBR) as a primary source of Cost Ingestion. The AWS Cost Explorer data is coming from the Cost and Usage Report (CUR). Moving forward, AWS is going to deprecate the DBR and we will therefore eventually only use the CUR.

For more info, see: https://success.cloudcheckr.com/article/7r000iwzex-transition-from-dbr-to-cur-faq

Question: Why do I have to configure the Cost and Usage Report?


The AWS Cost and Usage Report (CUR) is going to be the primary source of cost data that CloudCheckr will use to ingest in the future, as the Detailed Billing Report (DBR) is going to be deprecated by AWS.

Question: What is the standard CloudCheckr release cycle?


In a typical cycle, we release an update to the application every two weeks on Monday evenings EST.

Question: What can I do with the Dashboard section?


Dashboards give you quick, shareable overviews of your Cost, Inventory, Utilization, and Saved Filters.

For more info, see: https://success.cloudcheckr.com/article/8z32tr6yil-dashboards

Question: What can I do with Advanced Grouping?


Advanced Grouping is one of our most powerful tools, giving you total flexibility over cost data in your Detailed Billing Report (DBR). Advanced Grouping allows you to easily pivot your data and costs by multiple levels of DBR criteria, such as Account, Resource ID, Service, and Tag Keys. For instance, you can group costs by Tag Keys of CustomerName, then further group costs within that by Tag Key of ProductName. You can create reports of up to five levels of groupings with Tag Keys.

For more info, see: https://success.cloudcheckr.com/article/5s11l0k4fo-advanced-grouping-report

Question: What is the difference between CloudCheckr’s AWS, Azure, and GCP offerings?


We have a robust and aggressive plan for reaching feature parity of Azure to match AWS and bring high support to GCP. Please speak to your Account Executive for more information.

Question: Can Total Compliance be used to help passed my audit?


CloudCheckr's Total Compliance module presents both a point-in-time score for over thirty-five regulations as well as historical graphs showing the organization’s progress towards completeness. Total Compliance maps CloudCheckr's more than 550 Best Practice Checks to each framework, attesting to any cloud-based controls. These include IRS 1075, NIST frameworks, PCI DSS, HIPAA, FedRAMP, AICPA GAPP, NERC standards, NSA MNT and Top 10, FFIEC, and a number or international regulations including Saudi AMA, Australian Top 35 and Essential 8, and ISO 28002-2013, among others.

Question: How does Total Compliance relate to Best Practice Checks (BPCs)?


Total Compliance pulls its data from the CloudCheckr BPCs. Most of this data is then auto-populated in the Total Compliance report. However, there are a few ‘Controls’ within Total Compliance that need manual input or attestations from you as the user.

For more info, see: https://success.cloudcheckr.com/article/nn4248tbgn-total-compliance

Question: It’s the 3rd of the month -- why isn’t my AWS Bill finalized?


Amazon finalizes the bill anywhere between the 3rd and the 5th of the month. You should receive an email from them once the bill is finalized and should also see a notice in the AWS Console.

Once the bill is finalized and CloudCheckr picks up, we will display a message in the notification bubble letting you know the bill has been finalized and fully loaded into CloudCheckr.

How did we do?