Inconsistent limitation applied to CreateAnalysis call compared to Analysis console

Q&A
,
1

Since the general availability of the quicksight API’s allowing the creation of quicksight analysis we are trying to migrate our analysis into terraform code. However, we have an analysis which contains a large table of raw data which consists of over 200 ColumnConfigurations.

Terraform is rejecting the request with the following
│ No more than 200 “column_configurations” blocks are allowed

Which would appear to match the api documentation maximum for AnalysisDefinition.ColumnConfiguration.

However, we have previously already created this report directly for quicksight console, is it possible for this limitation to match the existing limits that are being applied by the console itself? So that pre-exisiting reports can actually be reproduced by the public apis?

2

Hi @j-short

If I understand correctly, you created an analysis in Quicksight using a dataset with more than 200 columns but the API for analysis definition has a built-in limitation of 200 columns per analysis. You are asking for this limitation to be removed so that the API can match QS UI capabilities, correct?
If yes, then I can take this down as a feature-request.

Let us know if this is resolved. And if it is, please help the community by marking this answer as a “Solution.”

Thanks!

3

HI @gillepa ,

This is correct, I would like the public API to match the QS UI capabilities so that our resources can be recreated in IaC (Terraform)