- Newest
- Most votes
- Most comments
The error you're encountering suggests that CloudFormation is unable to find the QuickSight data source after attempting to create it. This could be due to a few reasons:
-
Permissions: Ensure that the IAM role executing the CloudFormation template has the necessary permissions to create and manage QuickSight resources. The role should have appropriate QuickSight permissions, including the ability to create data sources.
-
QuickSight subscription: Verify that you have an active QuickSight subscription in the AWS account and region where you're deploying the stack. Without an active subscription, QuickSight resources cannot be created.
-
Resource naming: The
dataSourceIdyou've specified ("ds1") might not be unique or could be conflicting with an existing resource. Try using a more unique identifier or allowing CloudFormation to generate one automatically. -
Dependencies: Make sure that the Athena workgroup is fully created before the QuickSight data source tries to reference it. You might need to add a dependency to ensure the correct order of resource creation.
-
Region compatibility: Confirm that QuickSight is available and supports Athena integration in the region where you're deploying.
To troubleshoot:
- Double-check your IAM permissions and QuickSight subscription status.
- Try removing the
dataSourceIdproperty to let CloudFormation generate a unique ID. - Add an explicit dependency between the QuickSight data source and the Athena workgroup.
- Review CloudFormation logs and QuickSight console for any additional error messages.
If the issue persists, you may want to try creating the QuickSight data source manually through the AWS console to see if you encounter any specific errors that could provide more insight into the problem.
Sources
CreateDataSource - Amazon QuickSight
Creating a data source - Amazon QuickSight
DataSource - Amazon QuickSight
AssetBundleExportJobDataSourceOverrideProperties - Amazon QuickSight
Relevant content
asked a year ago
- AWS OFFICIALUpdated 2 months ago

The issue was that I hadn't created a QuickSight subscription yet. After setting it up manually, I was able to get past this issue.