[BUG] Cannot Create DirectQuery Athena Datasets in New Data Source Experience - Workaround Available

Q&A
, ,
1

Issue Summary

When creating a new Athena dataset in Quick Suite using the new data source experience, DirectQuery datasets fail to publish with the error:

Cannot publish dataset
Unable to update the dataset. If the issue persists, please contact the QuickSight support team

SPICE datasets work fine - this issue only affects DirectQuery mode.

Environment

  • Product: Quick Suite (formerly QuickSight)

  • Data Source: Amazon Athena

  • Dataset Mode: DirectQuery (live query)

  • UI: New expanded data source creation screen

  • Error Code: None provided (generic error message)

Steps to Reproduce

  1. Navigate to Datasets → New dataset

  2. Select Athena as data source

  3. Configure Athena connection (workgroup, database, table)

  4. Write custom SQL or select table

  5. Preview data successfully (validation passes)

  6. Select DirectQuery mode

  7. Click Publish or Save & publish

  8. Error appears: “Cannot publish dataset. Unable to update the dataset…”

Expected Behavior

DirectQuery Athena datasets should publish successfully, allowing live queries without importing data to SPICE.

Actual Behavior

Publishing fails with a vague error message. No additional details are provided in:

  • QuickSight UI error message

  • Dataset refresh history

  • CloudWatch logs

Note: The same query works perfectly when using SPICE mode instead of DirectQuery.

Workaround :white_check_mark:

Revert to the old QuickSight data source experience to create DirectQuery datasets:

Step-by-Step Fix

  1. Look for a toggle/link that says “Use legacy data source creation” or “Switch to old experience” (exact location may vary)

  2. Once in the old QuickSight UI, create your dataset as you normally would

    • Click Publish

  3. Dataset publishes successfully

Request to Quick Suite Team

Could the Quick Suite engineering team investigate the new data source creation flow for DirectQuery Athena datasets? The legacy UI works perfectly, suggesting this is a UI-layer regression rather than a backend/permissions issue.

Root Cause (Speculation)

The new Quick Suite data source UI appears to have a regression in the DirectQuery publishing flow. Possible causes:

  • Missing API parameters when switching from new UI to backend

  • Validation logic incorrectly rejecting valid DirectQuery configurations

  • IAM/permissions being checked differently in new vs. old UI

This does NOT appear to be an IAM permissions issue because:

  • SPICE mode works fine with same permissions

  • Old QuickSight UI works fine with same data source

  • Athena connection validates successfully

Impact

  • Severity: High (blocks DirectQuery dataset creation)

  • Scope: New Quick Suite data source experience only

  • Affected Users: Anyone creating new DirectQuery Athena datasets

  • Workaround Available: Yes (use legacy UI)

Additional Context

  • Athena queries work perfectly when executed directly in Athena Console

  • Connection validation passes in Quick Suite (sees database, tables, columns)

  • Data preview works in Quick Suite before attempting to publish

  • SPICE import works with identical configuration

  • Old QuickSight UI works with identical configuration

2 Likes
2

Does anyone know how long the “Use legacy data source creation” option will be available?

1 Like
3

Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!”