Error deploying Trends Dashboard using cid-cmd
Closed this issue · 1 comments
Hi,
Following the instructions here:
https://catalog.workshops.aws/awscid/en-US/dashboards/additional/trends
When I try to deploy the trends dashboard it seems to be looking for an aws_accounts athena view which doesn't exist.
It them tries to locate account metadata but can't. It asks for account metadata source, I choose Organizations and it breaks...
I have already deployed the foundational dashboards, Data Collector and TAO dashboard - all are working fine.
I've integrated the Organizations data into the account_map view, as per:
https://catalog.workshops.aws/awscid/en-US/dashboards/foundational/cudos-cid-kpi/add-accounts#option-3:-leverage-your-existing-aws-organizations-account-mapping-(recommended)
Please can you provide any guidance?
Console output:
[cloudshell-user@ip-XXXX ~]$ cid-cmd deploy --dashboard-id trends-dashboard
CLOUD INTELLIGENCE DASHBOARDS (CID) CLI 0.3.4 Beta
Loading plugins...
Core loaded
Checking AWS environment...
profile name: default
accountId: XXXX
AWS userId: XXXX
Region: eu-central-1
Latest template: arn:aws:quicksight:us-east-1:223485597511:template/cudos-trends-dashboard-template/version/4
Dashboard "trends-dashboard" is not deployed
Required datasets:
- monthly-anomaly-detection
- monthly-bill-by-account
- daily-anomaly-detection
Looking by DataSetId defined in template...complete
There are still 3 datasets missing: daily-anomaly-detection, monthly-anomaly-detection, monthly-bill-by-account
Creating dataset: daily-anomaly-detection
? [athena-workgroup] Select Amazon Athena workgroup to use: CID
? [quicksight-datasource-id] Please choose DataSource (Select the first one if not sure): CID-Athena CID-Athena (workgroup=CID)
? [athena-database] Select AWS Athena database to use: cid_cur
Detected views:
Missing views: daily_anomaly_detection
Missing dependency view: aws_accounts, creating
Checking if CUR is enabled and available...
? [cur-table-name] Please select CUR: XXXX
Athena table: XXXX
Resource IDs: yes
SavingsPlans: yes
Reserved Instances: yes
Creating account mapping aws_accounts
Autodiscovering metadata table
Account metadata not detected
? [account-map-source] Please select account metadata collection method: AWS Organizations (one time account listing)
Collecting account info from AWS Organizations
No access to AWS Organization.
0 accounts collected
Collecting account info from AWS Organizations
No access to AWS Organization.
0 accounts collected
Collecting account info from AWS Organizations
No access to AWS Organization.
0 accounts collected
CRITICAL - Failed to create account map
please choose dummy option first