← Back to all announcements
★★★☆☆ 04/05/2026

Amazon Quick introduces Dataset Q&A for conversational analytics against enterprise data

Ask your data anything in plain English and get instant answers without building dashboards or writing SQL queries.

View original announcement →

Visual Summary

graph TD A{{Dataset Q&A}}:::announced B((Business Users)):::external C([Text-to-SQL Agent]):::feature D([Knowledge Graph]):::feature E([Explain Capability]):::feature F(Amazon Redshift):::storage G(Amazon Athena):::storage H(SPICE):::storage I(Amazon S3 Iceberg):::storage J([RLS/CLS Governance]):::feature B ==>|"asks questions"| A A -->|"interprets via"| C C -->|"uses semantics"| D C -->|"generates SQL"| F C -->|"generates SQL"| G C -->|"generates SQL"| H C -.->|"generates SQL"| I A -->|"surfaces reasoning"| E A -->|"enforces"| J classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0 classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32 classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100 classDef external fill:#f5f5f5,stroke:#616161,color:#616161

What's New

Amazon Quick has launched Dataset Q&A, a conversational analytics capability that allows users to ask natural language questions directly against enterprise datasets. This feature complements the existing Dashboard Q&A functionality by enabling ad-hoc, open-ended data exploration beyond pre-built dashboards. Dataset Q&A is powered by a text-to-SQL agent that interprets questions, identifies relevant data, and generates optimized SQL in a single conversational step, all while enforcing existing governance policies such as Row Level Security (RLS) and Column Level Security (CLS).

How It Works

  • At its core, Dataset Q&A uses a text-to-SQL agent that translates natural language queries into engine- and dialect-aware SQL optimized for the target data source — including Amazon Redshift, Amazon Athena, Aurora PostgreSQL, Apache Iceberg tables in S3 table buckets, and SPICE.
  • Data owners can enrich datasets with custom instructions, business definitions, and field descriptions either inline within Amazon Quick or via file uploads.
  • These semantic annotations, combined with dataset metadata, are ingested into a knowledge graph that models the meaning and relationships across data assets.
  • An orchestrator layer uses this knowledge graph to identify the most relevant datasets and generate accurate SQL at query time.
  • The system supports a wide range of analytical question types — trend analysis, time-series comparisons, ranking, multi-condition queries, and exploratory questions.
  • An "Explain" capability surfaces the reasoning chain, the generated SQL, and the underlying logic so users can validate correctness before acting on results.

Why It's Important

  • Dataset Q&A significantly lowers the barrier to data access for non-technical business users by eliminating the need to write SQL or rely on pre-built dashboards for every analytical question.
  • Because it inherits and enforces existing RLS and CLS governance policies, organizations can safely expose this capability to a broad user base without compromising data security or compliance.
  • The knowledge graph approach means that semantic context — business terminology, field relationships, and domain-specific definitions — is preserved and reused across queries, improving accuracy and reducing the need for repeated prompt engineering.
  • The Explain feature also builds user trust by making the AI's reasoning transparent and auditable, which is critical for enterprise adoption of AI-driven analytics.

How It's Different

  • Prior to Dataset Q&A, Amazon Quick's natural language capability was primarily scoped to Dashboard Q&A, which allowed users to ask questions within the context of an already-built dashboard and its pre-defined visuals.
  • Dataset Q&A removes that constraint, enabling direct, schema-level interrogation of raw datasets without requiring a dashboard to exist first.
  • Compared to generic text-to-SQL tools or standalone LLM integrations, Dataset Q&A is tightly integrated with Quick's governance layer, ensuring security policies are automatically applied rather than bolted on.
  • The knowledge graph enrichment model also differentiates it from simpler prompt-based SQL generators, as it captures persistent semantic context that improves query accuracy over time and across users — rather than relying solely on the LLM's in-context understanding of schema metadata.

When to Prefer It

  • Dataset Q&A is the right choice when business users need to perform ad-hoc, exploratory analysis against enterprise datasets without waiting for a BI developer to build or modify a dashboard.
  • It is particularly well-suited for organizations with large, complex data estates where users may not know which dataset to query or how fields relate to one another — the knowledge graph handles dataset discovery and disambiguation automatically.
  • Teams that have already invested in defining RLS/CLS policies in Amazon Quick will benefit immediately, as those controls are enforced without additional configuration.
  • For use cases requiring auditability of AI-generated insights — such as financial reporting, compliance analytics, or executive decision-making — the Explain capability makes Dataset Q&A preferable to black-box alternatives.
  • It is less appropriate when highly complex, multi-step analytical workflows require custom SQL logic that exceeds what a text-to-SQL agent can reliably generate, or when the underlying datasets lack sufficient semantic enrichment to guide accurate query generation.

Availability

  • Dataset Q&A is generally available (GA) as of May 4, 2026, and is accessible in all AWS Regions where Amazon Quick is currently supported.
  • No preview or limited-access period is indicated — the feature is fully released for production use.
  • Supported data sources include Amazon Redshift, Amazon Athena, Aurora PostgreSQL, Apache Iceberg tables stored in Amazon S3 table buckets, and SPICE.
  • There are no explicitly stated regional exclusions, though availability is contingent on Amazon Quick itself being available in a given region.
  • Organizations should ensure their datasets are enriched with business definitions and field descriptions to maximize query accuracy, as the quality of the knowledge graph directly influences the reliability of generated SQL.

Tags

Servicesquick
Typega-launchnew-feature
Conceptsconversational-aigenaidata-analyticsnlp
Use Casesenterprise
GeographyGlobal

AI Radar AWS

AWS AI/ML news — curated, researched, explained

An automated intelligence platform that curates, researches, and analyzes AWS AI/ML/GenAI announcements daily. Every report is backed by real research — the system reads linked blog posts and documentation to provide accurate, in-depth analysis.

How Each Report Is Generated

  1. Collection — Daily monitoring of the AWS "What's New" RSS feed
  2. Filtering — AI-powered relevance detection for AI/ML/GenAI topics
  3. Taxonomy Tagging — LLM-based classification across 6 dimensions
  4. Importance Scoring — Point-based system with tag bonuses (1-5 stars)
  5. Research Phase — Follows links to blog posts and documentation
  6. Report Generation — Claude Sonnet produces structured 6-section analysis
  7. Visual Summary — Claude Opus generates Mermaid diagrams for key items
  8. Publishing — Static website rebuilt and deployed via CloudFront

Features

  • Faceted filtering by service, type, concept, and more
  • Multi-dimensional taxonomy with 80+ tags across 6 dimensions
  • Geographic availability badges (Global, APJ, EMEA, AMER) with filtering
  • Timeline visualization of announcement volume
  • PDF export for offline reading
  • Mermaid visual summaries for key announcements
  • Daily automated updates — no manual curation
What makes this different: Each report involves a dedicated research phase where the system reads linked blog posts and AWS documentation pages. This produces analysis that goes beyond the original announcement text.

Technology

Built with Python, AWS Lambda, Amazon Bedrock (Claude Sonnet 4.6, Opus 4.6, Haiku 4.5), S3, CloudFront, WAF, EventBridge, and CDK.

Open Source

This project is open source. Fork it, customize it for your needs, and deploy your own instance.
📦 github.com/bbonik/ai-radar-aws

How Importance Scoring Works

Each announcement receives a point score based on multiple factors. The total score maps to a 1-5 star rating:

1★ < 2 pts 2★ ≥ 2 pts 3★ ≥ 3.5 pts 4★ ≥ 5 pts 5★ ≥ 6.5 pts

Point Breakdown

FactorPointsWhen
Core AI service (Bedrock, AgentCore, SageMaker AI)+4Service named in title
Key AI service (SageMaker, Kiro, QuickSight)+2Service named in title
Other AI-related service+1Default
Blog post link+3Link to aws.amazon.com/blogs/
GitHub samples link+2Link to github.com/aws*
Documentation link+1Link to docs.aws.amazon.com/
New model+1.5Tagged as "new-model"
New service+1Tagged as "new-service"
New feature+0.5Tagged as "new-feature"
Anthropic / OpenAI provider+2Provider explicitly mentioned
Instance / notebook announcement-2Hardware/capacity, not feature
Performance / pricing / security-0.5Incremental updates
Region expansion to APJ+1Expands to Asia Pacific
Region expansion (non-APJ only)-1.5Only expands to other regions

Geographic Relevance Badges

Each announcement card shows a small badge indicating whether the feature is available in your region:

🌐 Global Available in all regions
🌏 APJ Asia Pacific
🌍 EMEA Europe / Middle East / Africa
🌎 AMER Americas (US, Canada, South America)
No badge Geography unknown
How geography is detected: The system detects ALL geographies mentioned in each announcement. If the text mentions specific regions (Tokyo, Frankfurt, Oregon, etc.), the corresponding geography badges are shown. If it says "all regions" or is a new feature with no region specified, it gets the Global badge. Geography is also filterable — click a geo chip to see only announcements available in that region.