AWS::QuickSight::Analysis: Parameters to Define Visualizations in an Analysis

[bretticus-mc]

Describe the feature

There is no way to define visualizations in QuickSight::Analysis at this time. The only work around I've found is to first create an Analysis with the needed visualizations manually in the UI console. Then I have to reference the ARN of that Analysis in a programmatically created Analysis containing the desired DataSets. This means we can only automate dashboards that use the same DataSet Schema and visualizations.

Each dashboard with different visualizations or schema currently requires an Analysis to be manually created. This severely limits the use-case of the QuickSight CDK as a whole.

Use Case

We want to fully automate the creation of QuickSight dashboards. There should not be a manual step required to create a dashboard programmatically. Being able to define visuals programmatically will also provide full version control of the dashboards we create.

Proposed Solution

We need more parameters in the Analysis construct in order to define the visuals that populate our dashboards. Maybe it could even take a JSON payload containing all parameters of the visualizations.

Other Information

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_quicksight.CfnAnalysis.html

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.31.1

Environment details (OS name and version, etc.)

Mac OS Monterey 12.3.1

[peterwoodworth]

We don't have any L2 constructs for QuickSight, or in other words, we don't have any abstractions from CloudFormation resources.

If it's the CloudFormation resource itself that you want a new feature for, the best place to ask for that is to ask the CloudFormation team. They have a coverage roadmap where you can submit a request for new features to cloudformation https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues

once this is added to CloudFormation, CDK will automatically support it. Until then, there's not much we can do here to implement this ourselves