Amazon Quick Apps can now query governed Quick Sight data live

From frozen snapshots to live queries

Quick Apps already pulled live content at view time from action connectors such as Jira, Slack and Google Drive, from Spaces documents, web search and AI inference. Governed Quick Sight datasets were the gap. The SPICE and Direct Query tables that hold business metrics could not be queried live from an app, and any dataset figures an app displayed were baked in when the agent built it, according to AWS.

Amazon Quick is described by AWS as an AI-powered unified intelligence service that connects governed enterprise data and content. With Quick Apps, users describe an application in plain language and an AI agent writes and deploys a working web application, with no hands-on coding or DevOps steps required.

With Live Data in Apps, the agent finds relevant curated datasets on its own and writes the SQL needed to answer the question while building the app. After publishing, the app re-runs that SQL every time someone opens it, so the numbers are current.

Building, consent and security

AWS walks through an example for a fictional SaaS provider, AnyCompany, whose regional sales leaders review deal renewals. A sales leader opens Apps in Amazon Quick and enters a prompt asking for customer renewals in the current quarter and the next 6 months, with revenue and margin shown when a customer is chosen. The agent discovers the SaaS Sales and Customer Renewals datasets, writes the SQL and asks the builder to approve each dataset by name.

The leader can then add features with further prompts, such as an AI summary overlay that combines the revenue dataset with an enterprise product strategy document. A Manage integrations pop-up lists every integration the app uses. Once published, the app can be shared with viewer access to Quick users or groups.

Viewers are prompted for consent the first time they open the app. AWS says existing row-level security (RLS) and column-level security (CLS) rules apply automatically, and that consent is enforced on the server side on every query. In the example, a manager with AMER access sees only AMER data, while a manager with both EMEA and AMER access sees both. Users who lack access to the underlying datasets get an access error.

Requirements and what it means for teams

AWS lists several prerequisites:

• Datasets must already exist, with or without RLS and CLS.
• Both SPICE (in-memory) and Direct Query datasets are supported.
• Each viewer must consent per dataset on first use, and builders approve datasets during the build.
• Viewers must be authenticated Quick users. Anonymous or public access is not supported for apps using live datasets.
• The minimum role for a builder or user is Reader Pro (Professional).

For business operations owners, AWS says the feature removes manual data refresh, snapshot management and custom API plumbing. For administrators, no new permission model is needed. In the AnyCompany example, AWS says a task that would typically take a month of effort can be built by a sales leader from a dataset they already have access to and shared without waiting for IT.