Painful Experience Migrating to CUR 2.0 - WorkGroup is not found

Question & Answer
,
1

I am trying to upgrade our existing Cloud Intelligence Dashboards (CID) to the CUR2 version, following the guidance outlined in the Cloud Intelligence Dashboards Framework’s Migration to CUR 2.0 document. We’ve encountered several issues during the process that have significantly impacted our progress.

Step 2.1: CloudFormation Update

  1. Rollback Setting Not Addressed
    The initial CloudFormation update failed due to the default rollback setting being disabled. This critical configuration detail was not mentioned in the documentation, which made troubleshooting more difficult. Including this in the instructions would be very helpful.

  2. Lambda Function Conflict
    The CustomResourceFunctionInit resource failed because the Lambda function CidInitialSetup-DoNotRun${Suffix} already existed — likely due to this being an upgrade from an existing stack. There was no guidance on how to handle this conflict. I worked around it by renaming the function in the template, but this feels like an unsupported workaround. Ideally, the template should handle this scenario or the documentation should provide clear instructions.

  3. Missing Dataset: customer_all
    The stack failed with the following error:
    4.“Failed to find a Dataset ‘customer_all’ with required fields…”*
    After investigation, I found this was tied to the deprecated CUDODashboard(v4) section, which defaults to “yes” in the parameters. This was not mentioned in the migration instructions. Setting this to “no” allowed the stack to succeed.

Step 2.2: Command Line Update

  • After updating cid-cmd via pip, I ran cid-cmd update --force --recursive. Contrary to the documentation, it did not prompt me to select a CUR.
  • Attempting to update the CUDOS Dashboard v5 resulted in the following error:
    “An error occurred (InvalidRequestException) when calling the GetWorkGroup operation: WorkGroup is not found.”
  • The same error occurred when updating the Cost Intelligence Dashboard.

Additionally, the documentation states that the tool will show a diff between current and updated Athena views, allowing the user to proceed or manually adjust. I did not receive any such prompt or diff output.

Could you please advise on the following:

  • How to resolve the WorkGroup is not found error during the dashboard update process?
  • Whether there are updated instructions or best practices for handling upgrades from existing CID stacks?
  • If there is a way to manually inspect or override the Athena view updates when the diff is not shown?

This upgrade process has been unexpectedly complex due to missing documentation and unhandled edge cases in the CloudFormation templates. Any guidance or updated resources you can provide would be greatly appreciated.

2

Hello @schwinbp welcome to the QuickSight community!

My hunch is that this is probably causing the downstream error.

I recommend reaching out to them directly at cloud-intelligence-dashboards@amazon.com to outline all of your findings plus the issue with the command line update.