AWS: Onboarding

These Frequently Asked Questions (FAQs) answer the most common questions we get asked about onboarding to CloudCheckr.

Question: How does CloudCheckr calculate my invoice?


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.

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 while 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 CloudCheckr process my cost data?


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 instructions:

Question: How does CloudCheckr process inventory, Best Practice Checks (BPCs), security, and utilization data?


These CloudCheckr modules get picked up through our Discovery process, a background job which is updated once a day by default. To manually kick this job off, click the Notification message in the top header bar and from the Reports Updated section, click Update.

Question: What can I do with the API?


Although you can access the same data in our UI, accessing the data via the API or programatically allows you and your admins to streamline and better manage your processes. For more information, review the API User Guide.

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


CloudCheckr is currently using the legacy AWS Detailed Billing Report (DBR) as a primary source of cost ingestion. The source for the AWS Cost Explorer data is the Cost and Usage Report (CUR). Moving forward, AWS will deprecate the DBR and at that point, CloudCheckr will only use the CUR.

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

Question: Why do I have to configure the CUR?


Since the CUR will be the primary source of cost data that CloudCheckr in the near future, you must configure the report in AWS and in CloudCheckr as soon as possible in order to make the smoothest transition.

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 Eastern Standard Time (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 information, review the Dashbhoards topic.

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 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 group costs within that by Tag Key of ProductName. You can create reports with up to five levels of groupings with tag keys.

For more information, review the Advanced Grouping Report topic.

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


We have an aggressive plan for reaching feature parity in Azure to match AWS and bring more support to our GCP offering. Please speak to your Account Executive for more information.

Question: Can I use Total Compliance to pass my audit?


CloudCheckr's Total Compliance module provides a point-in-time score for more than 35 regulations and historical graphs showing an organization’s progress towards completeness. Total Compliance maps CloudCheckr's 550-plus BPCs to each framework, attesting to any cloud-based controls. These frameworks include IRS 1075, NIST, 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 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 information, review the Total Compliance topic.

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 AWS once the bill is finalized and you hould also see a notice in the AWS Console.

Once the bill is finalized and CloudCheckr picks it up, the application will display a notification message to let you know that the bill is final and fully loaded in CloudCheckr.

How did we do?