"Cost Explorer Query Failure" alert in CPM 3.0

"Cost Explorer Query Failure" alert in CPM 3.0

After upgrading to CPM 3.0, you may see an Alert in the console which says "Cost Explorer Query Failure". 

If you view the Alert, you will see an AccessDeniedException:





The cause of this alert is due to the CPM role permissions not being updated with the latest JSON files.  You can download the latest files from the link at the bottom of this document:






 

    • Related Articles

    • Troubleshooting common Cost Explorer issues

      This  document will go through the steps one can take to resolve common issues related to the CPM Cost Explorer feature   1.  Required Permissions Make sure that you have updated the CPM instance role and all users associated with CPM with the latest ...
    • Upgrade instructions for v2.7.0

      This guide outlines the steps required to upgrade to N2WS Backup & Recovery version 2.7. We strongly recommend that you follow every step contained within this guide to ensure version 2.7 is configured correctly and no data loss occurs. Customers ...
    • CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors

      CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist"  and "Configuration Failed" errors: The reason for this failure is using wrong AWS Access Key and Secret Key - maybe they belong to the wrong account.
    • Patch for cost reduction of copy to S3

      Installation of the patch will reduce costs drastically for customers who are using S3 (Between 5 to 20 times less expensive than previous version) The improvements are: For copied volumes which are larger than 512GB, worker’s volume type will be sc1 ...
    • CPM may not retry Tag Scanning if scanning fails due to RequestLimitExceeded

      If Tag scanning is triggered and fails due to RequestLimitExceeded, an alert is generated and no retry is scheduled. Please search for the below print in the server log: ERROR:  scan_resources(backup_tag.py:<line_number))  Failed getting <resources> ...