Amazon Q isn’t one bundled product. It’s AWS’s brand for generative AI assistants built into individual services: Amazon Q Developer, which includes a Glue ETL-authoring feature, and Amazon Q Business. AWS Glue’s own Data Catalog hasn’t moved, and Atlan’s context layer has to keep working no matter what AWS calls its BI layer this quarter. QuickSight, the BI tool one of those assistants used to plug into, was renamed Amazon Quick Suite on 9 October 2025, and AWS’s live documentation now says Amazon Quick. Amazon Q Business itself closed to new customers on 30 July 2026, folding into Amazon Quick.
That’s only the AI-assistant half of the story. Underneath the Glue-side assistant sits AWS Glue Data Catalog, the technical metadata store it reads from. Atlan’s AWS Glue and QuickSight connectors pull that metadata, including the types of metadata an agent actually needs, into one Enterprise Data Graph, then serve it to agents outside the AWS boundary through Atlan’s MCP server. None of AWS’s Q-branded assistants can see past their own service.
- Amazon Q is a family, not a package. Q Developer, which includes the Glue ETL feature, and Q Business ship and bill separately.
- QuickSight is now Amazon Quick. The chain runs QuickSight Q (preview 2020, GA 2021) to Amazon Q in QuickSight (preview 2023, GA 2024) to Amazon Quick Suite (October 2025) to Amazon Quick (2026).
- Amazon Q Business closed to new signups on 30 July 2026, with AWS steering new use cases toward Amazon Quick instead.
- AWS Glue Data Catalog is the one constant. It hasn’t been renamed, and the Q assistant inside Glue still reads from it.
Below: what Amazon Q actually is, the QuickSight rename timeline, how Q shows up inside Glue, what survives the rename, what happens to Q Business customers, how the three Q surfaces compare, and how a context layer fits underneath it.
| Field | Detail |
|---|---|
| What Amazon Q is | AWS’s brand for generative AI assistants built into individual services: Q Developer (which includes a Glue feature) and Q Business |
| What happened to QuickSight | Renamed to Amazon Quick Suite on 9 October 2025; AWS’s live documentation now says Amazon Quick |
| Amazon Q Business status | Closed to new customers 30 July 2026; existing customers keep patches, no new features |
| Amazon Q + AWS Glue | A live, narrow assistant that writes and troubleshoots Glue ETL jobs and references the Glue Data Catalog |
| What hasn’t changed | AWS Glue Data Catalog, the metadata store the Glue-side assistant reads from, a fragmentation problem the Multi-Cloud Context Layer approach was built to sit above |
What is Amazon Q, and is it one product or several?
Amazon Q names several separate assistants, each with its own user guide, pricing, and subscription, rather than one package. AWS documents them one at a time: Amazon Q Developer has its own guide and its own pricing page, Amazon Q Business has another, and the BI assistant now bills as part of Amazon Quick. There is no single AWS page that defines Amazon Q as one family.
Three surfaces currently carry the Q name. Amazon Q Developer handles coding help, AWS troubleshooting, and the Glue data-integration feature covered below. Amazon Q Business handles enterprise search and chat over connected documents and apps, though it closed to new customers this year. The assistant that used to live inside QuickSight now sits inside Amazon Quick, the renamed platform covered in the next section.
The “bundle” framing took hold because Q genuinely touched both QuickSight and Glue at different times. Q Developer, Q Business, and the QuickSight assistant have always been priced and subscribed separately. That distinction matters for anyone trying to trace where their AI agent context actually comes from inside an AWS stack: three assistants, three different scopes, one shared brand name, and an AI context platform question underneath all of them about whether any one of these surfaces sees the whole picture. None of them does on its own.
Did Amazon QuickSight get renamed to Amazon Quick?
Yes. QuickSight has been renamed twice since 2024: first to Amazon Quick Suite, then, within months, shortened again to Amazon Quick. This isn’t a cosmetic label change. AWS repositioned the whole product around agentic workflows, and the BI capability that used to be the entire product became one component inside something wider.
QuickSight Q to Amazon Q in QuickSight (GA April 30, 2024)
QuickSight Q launched in preview in December 2020 as a natural-language question-and-answer layer on top of QuickSight dashboards, reaching general availability the following year. Its generative AI-powered successor, Amazon Q in QuickSight, launched in preview at AWS re:Invent 2023 for existing QuickSight Q subscribers. According to AWS’s BI Blog (April 30, 2024), “Amazon Q in QuickSight is the generative AI-enhanced upgrade of the previous QuickSight Q,” now generally available to every user in an organization, not just a licensed subset.
Amazon Q in QuickSight to Amazon Quick Suite (October 9, 2025)
Eighteen months later, AWS rebuilt the product again. AWS’s BI Blog (October 9, 2025) announced that Amazon QuickSight evolves to Amazon Quick Suite, folding BI into a wider agentic workspace. More than a console refresh: the product picked up research, automation, and agent surfaces the BI tool never had. QuickSight’s BI capability continues inside it as a component AWS’s feature table calls “Quick Sight,” with a space.
Amazon Quick Suite to Amazon Quick (no dated announcement)
The name shortened again, to simply Amazon Quick. AWS published no announcement and no date for that one. What it did do is move the documentation: the user guide now sits at docs.aws.amazon.com/quick/ and says Amazon Quick throughout, while the pricing page URL still reads /quicksuite/ and the page text says Amazon Quick. A rename you can only date by watching the docs move is the kind of thing that leaves a stack of half-current internal runbooks behind it.
Table: The Amazon QuickSight rename timeline
| Date | Name | What changed |
|---|---|---|
| December 2020 | QuickSight Q (preview) | First natural-language Q&A layer added to QuickSight; reached general availability in 2021 |
| November 2023 | Amazon Q in QuickSight (preview) | Generative AI-powered upgrade to QuickSight Q, previewed at AWS re:Invent 2023 for existing QuickSight Q subscribers |
| April 30, 2024 | Amazon Q in QuickSight (GA) | Amazon Q in QuickSight becomes generally available to every user in an organization |
| October 9, 2025 | Amazon Quick Suite | QuickSight evolves into a wider agentic workspace; BI capability continues inside it as “Quick Sight” |
| Undated | Amazon Quick | “Amazon Quick Suite” shortened to “Amazon Quick”; the user guide moved to docs.aws.amazon.com/quick/ with no announcement |
| 30 July 2026 | Amazon Q Business closed to new customers | Existing customers keep bug fixes and security updates; no new signups; AWS recommends migrating to Amazon Quick |
| 30 April 2027 | Amazon Q Developer IDE plugins end of support | AWS’s Q Developer guide names Kiro as the replacement |
The same platform-native churn shows up elsewhere. Databricks reorganized its Genie stack around a live ontology in 2026 (see Genie Ontology and the Atlan Context Layer), and Snowflake ran its own version of the pattern (see Snowflake Horizon Context and the Atlan Context Layer and Snowflake Cortex Sense). AWS renaming QuickSight twice in two years is the same story with a different vendor’s name on it.
Get the AI Context Stack brief
A short guide to keeping context stable when every cloud vendor is renaming its AI layer at once.
Get the AI Context StackAmazon Q’s role inside AWS Glue and the Glue Data Catalog
Inside AWS Glue, Amazon Q is a narrow, live assistant that helps write and troubleshoot ETL jobs, and it explicitly references the Glue Data Catalog as one of the things it can answer questions about. This is the one piece of the original “bundle” premise that’s real, current, and still shipping under the Q name.
AWS’s own Glue Developer Guide lists AWS Glue Data Catalog among the domains the assistant answers questions about, with a listed example prompt: “Help me develop an AWS Glue script for AWS Glue Data Catalog to S3.” The feature first shipped in preview per AWS’s What’s New post (January 30, 2024) and reached general availability three months later. According to AWS’s Big Data Blog (April 30, 2024), the capability ships under Amazon Q Developer, not Q Business, a distinction AWS makes explicitly in its own naming.
The scope is narrow and AWS states it plainly: Amazon Q in Glue chats about Glue and data integration, generates PySpark scripts, and troubleshoots jobs. Those three capabilities are what AWS documents. Glue’s own business context arrived separately, in a June 2026 preview covered below, not through the assistant. A broader data catalog for AI sits at a different altitude, because the Glue assistant answers questions inside one service. That’s the same scoping question a context layer versus a plain data catalog runs into anywhere metadata needs to travel past one vendor’s console, and it’s related to whether a catalog alone can work as an LLM knowledge base in the first place.
What survives the rename, in AWS’s own words
The BI tool did not go away. AWS’s feature table for Amazon Quick lists Quick Sight, with a space, as the component for “interactive dashboards and analytics,” alongside Quick Flows, Quick Automate, Quick Research, Apps in Quick, and a desktop application. A team that bought QuickSight for dashboards still has dashboards; it now reaches them through a product with four other surfaces attached and a different name on the console.
Two things follow for anyone documenting an AWS stack. Internal runbooks that name QuickSight point at a product name AWS no longer uses, and links to docs.aws.amazon.com/quicksuite/ need repointing to /quick/. Neither breaks anything today. Both make an estate harder to describe accurately, which is the same problem an AI agent hits when it reads those runbooks as context.
Amazon Q Business’s closure to new customers, and the migration path to Amazon Quick
Amazon Q Business stopped accepting new customers on 30 July 2026, and AWS is positioning Amazon Quick as where those customers, and their use cases, go next. The date comes from AWS’s own Service Availability Updates post of 30 June 2026, which lists the services moving to maintenance and states that they “will no longer be accessible to new customers starting July 30, 2026.” That post also closed Amazon Kendra and moved Amazon Bedrock Agents to Bedrock Agents Classic on the same date, so the consolidation is wider than the Q brand. AWS’s live Q Business pages now carry no date at all, only that the service is no longer open to new customers.
What happens to existing Amazon Q Business customers
AWS’s own availability-change documentation states AWS “will continue to provide bug fixes and security updates for existing customers, however new feature requests will no longer be considered.” It publishes no forced shutdown date. It also names the destination in its own words: “Amazon Quick represents the next evolution of Amazon Q Business,” and recommends customers migrate their Q Business applications and build new generative or agentic AI solutions on Amazon Quick.
New Q Business signups are no longer an option, so for a reader already running it, the practical takeaway is a migration conversation to plan with AWS, not a hard cutover deadline: AWS hasn’t published a forced shutdown date, so this is about choosing when to move to Amazon Quick, not a deadline you’ve already missed. If Q Business already sits inside a broader AWS deployment, that migration touches whatever depends on it: connected apps, indexed documents, and any workflow built around its enterprise search.
Amazon Q Developer vs Amazon Q Business vs Amazon Q in QuickSight or Quick: what’s the difference?
The three surfaces that carry the Amazon Q name do different jobs: one writes code and Glue scripts, one answers enterprise questions over documents, and one now lives inside Amazon Quick’s BI experience.
Amazon Q Developer covers coding assistance, AWS troubleshooting, and Glue ETL script authoring, and it carries an end-of-support notice of its own: AWS ends support for Amazon Q Developer IDE plugins on 30 April 2027, pointing users to Kiro. Amazon Q Business covers enterprise search and chat over connected documents and apps, and it closed to new customers on 30 July 2026. Amazon Q in QuickSight covered generative BI and natural-language querying, and now sits inside Amazon Quick. Larry Dignan, Editor in Chief of Constellation Insights at Constellation Research (April 28, 2026), an independent analyst rather than an AWS spokesperson, described Amazon Quick as functioning like “a desktop companion that leverages multiple agents and a context graph based on various enterprise systems.” Esra Kayabali, Senior Solutions Architect, and Donnie Prakoso, Principal Developer Advocate at AWS, describe the launch as bringing “AI-powered research, business intelligence, and automation capabilities into a single workspace.”
Table: The three Amazon Q surfaces compared
| Q surface | What it does | Where it lives | Status today |
|---|---|---|---|
| Amazon Q Developer | Coding help, AWS troubleshooting, Glue ETL script authoring | IDE, AWS console, AWS Glue | Active; AWS ends support for the IDE plugins on 30 April 2027 and points users to Kiro |
| Amazon Q Business | Enterprise search and chat over connected apps and documents | Q Business console | Closed to new customers 30 July 2026; migrating to Amazon Quick |
| Amazon Q in QuickSight | Generative BI, natural-language querying | Now inside Amazon Quick (formerly standalone QuickSight) | Active, rebranded as part of Amazon Quick |
Three differently-branded assistants, each scoped to its own AWS surface, are hard to judge against context layer evaluation criteria as one thing. That’s exactly the fragmentation pattern a cross-estate context graph sits above rather than replicates inside one vendor’s console. It’s a different problem than a context layer versus a plain vector database solves: fragmentation across services, not a retrieval choice inside one of them.
Find your AWS context gaps
See where Amazon Q, Amazon Quick, and Glue Data Catalog leave gaps in context an agent would need to answer accurately.
Try the Context Gap CalculatorHow Atlan approaches AWS’s renamed AI and BI layer
Even inside one vendor’s stack, AI context is fragmented across differently-branded, frequently-renamed touchpoints: Q Developer, Q Business, and Q in QuickSight or Quick. Underneath the Glue-side piece of that fragmentation sits AWS Glue Data Catalog. Its glossary terms arrived in a June 2026 preview, in four Regions, not general availability, and its catalog federation reads remote Iceberg catalogs including Snowflake Polaris and Databricks Unity. The reach is real, and it is reach to tables. Glossary terms, ownership, and policy still live per-service.
Atlan’s AWS Glue connector crawls databases, tables, and partition-level detail out of Glue Data Catalog into Atlan’s Enterprise Data Graph, following the same metadata management approach Atlan uses across every connected system. Atlan’s Amazon QuickSight connector, whose name hasn’t changed even though AWS renamed the product it connects to, carries lineage from source data into QuickSight’s dashboards, analyses, and datasets. Atlan’s MCP server then serves that governed, cross-estate context to agents outside the AWS boundary, including systems Q’s per-service assistants can’t see, a distinction from plain function calling that matters once an agent needs to reason across more than one AWS console.
Atlan doesn’t replace Glue Data Catalog or Amazon Quick. It unifies what each already knows with everything else in the estate, the same way data contracts formalize what a schema promises without replacing the schema itself. If you’re evaluating what to implement first when Glue Data Catalog alone isn’t enough, that’s the starting question: not which Q surface to pick, but how the context underneath all of them gets governed once.
See how ready your context layer is
Run the numbers on what a unified context layer would return once Amazon Q, Amazon Quick, and Glue Data Catalog all feed into it.
Try the Context Layer ROI CalculatorWhat AWS’s renamed AI layer means for your context strategy
Amazon Q Business closed to new signups on 30 July 2026, and AWS Glue Data Catalog is the one name in this stack that did not move. Everything else did. Q Developer, Q Business, and the QuickSight assistant each ship, bill, and subscribe separately, QuickSight is now Amazon Quick, and Q Developer’s IDE plugins have an end-of-support date of their own in April 2027.
The naming will likely change again. AWS renamed QuickSight twice in under two and a half years, and Q Business’s own migration into Quick shows the brand family isn’t done consolidating. What doesn’t change is the underlying need: context that survives a rebrand, whether that’s an AI agent harness that keeps pointing at the right assistant regardless of what AWS calls it, or context engineering that treats naming churn as an input to plan for. A semantic layer on top of Glue Data Catalog, governed per an AI governance framework and delivered through Atlan’s MCP-connected data catalog, doesn’t need rebuilding every time AWS ships a new name for the same service.
Check your context maturity
See how ready your context layer is to survive the next AWS rename, or the one after that.
Take the Maturity AssessmentFAQs about Amazon Q, QuickSight, and Glue
1. What is the difference between Amazon Q and Amazon QuickSight?
Amazon Q is AWS’s brand for a family of separate generative AI assistants built into individual services. Amazon QuickSight was AWS’s BI tool, and one of those assistants, Amazon Q in QuickSight, plugged into it starting in 2024. QuickSight itself was renamed Amazon Quick Suite in October 2025, and AWS’s live documentation now says Amazon Quick, so the two names now describe different things: an AI-assistant family and a renamed BI platform.
2. What is Amazon Q data integration in AWS Glue?
It’s a generative AI assistant, part of Amazon Q Developer, that helps write, troubleshoot, and understand AWS Glue ETL jobs through natural-language chat. AWS’s own docs list AWS Glue Data Catalog among the topics it can answer questions about, including example prompts for building scripts that read from the Data Catalog. It’s a narrow authoring tool, not a data catalog itself.
3. Is Amazon QuickSight still called QuickSight, or is it Quick Suite or Amazon Quick now?
AWS renamed QuickSight to Amazon Quick Suite on 9 October 2025, and its live documentation now says Amazon Quick, with the user guide at docs.aws.amazon.com/quick/. AWS published no dated announcement for that second shortening. QuickSight’s original BI capability still exists inside Amazon Quick as a component AWS’s feature table calls Quick Sight.
4. Is Amazon Q Business shutting down?
Not immediately, but it closed to new customers on 30 July 2026, the date AWS gives in its June 2026 Service Availability Updates post. Existing customers keep bug fixes and security updates, with no new feature requests considered and no published shutdown date. AWS’s own words are that “Amazon Quick represents the next evolution of Amazon Q Business,” and it recommends migrating there.
5. Does Amazon Q use the AWS Glue Data Catalog?
The Amazon Q assistant embedded in AWS Glue does. AWS documents the Glue assistant answering questions about the Data Catalog and generating scripts that read it, with a listed example prompt for building a script from the Data Catalog to Amazon S3. The Data Catalog itself is a separate AWS service that kept its name through every rename around it.
6. What’s the difference between Amazon Q Developer, Amazon Q Business, and Amazon Q in QuickSight or Quick?
Q Developer handles coding help, AWS troubleshooting, and Glue ETL authoring, and AWS ends support for its IDE plugins on 30 April 2027, naming Kiro as the replacement. Q Business handles enterprise search and chat over connected apps and documents, and it closed to new customers on 30 July 2026. Q in QuickSight was the generative BI assistant, now positioned inside Amazon Quick rather than standalone QuickSight. Each is scoped to its own AWS surface.
7. What is the purpose of Amazon Q in Amazon QuickSight?
Amazon Q in QuickSight, now part of Amazon Quick, answers natural-language questions over BI data, writes executive summaries, and generates visuals automatically, so business users get generative BI without writing SQL. AWS folded this capability into Amazon Quick Suite in the October 2025 rename. The generative BI capability now runs as Quick Sight inside Amazon Quick.
Sources
- What is Amazon Q Developer?, AWS Documentation. https://docs.aws.amazon.com/amazonq/latest/aws-builder-use-ug/what-is.html
- Amazon Q Developer IDE plugins end of support, AWS Documentation. https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-developer-ide-end-of-support.html
- Amazon QuickSight evolves to Amazon Quick Suite, AWS Business Intelligence Blog (October 9, 2025). https://aws.amazon.com/blogs/business-intelligence/reimagine-business-intelligence-amazon-quicksight-evolves-to-amazon-quick-suite/
- How Amazon Quick works, AWS Documentation. https://docs.aws.amazon.com/quick/latest/userguide/how-quicksuite-works.html
- Amazon Quick pricing, AWS. https://aws.amazon.com/quicksuite/pricing/
- Amazon Q data integration in AWS Glue, AWS Glue Developer Guide. https://docs.aws.amazon.com/glue/latest/dg/q.html
- Announcing Amazon Q data integration in AWS Glue (Preview), AWS What’s New (January 30, 2024). https://aws.amazon.com/about-aws/whats-new/2024/01/amazon-q-data-integration-aws-glue-preview
- Introducing Amazon Q data integration in AWS Glue, AWS Big Data Blog (April 30, 2024). https://aws.amazon.com/blogs/big-data/introducing-amazon-q-data-integration-in-aws-glue/
- AWS Service Availability Updates, AWS What’s New (June 30, 2026). https://aws.amazon.com/about-aws/whats-new/2026/06/aws-service-availability/
- AWS Glue Data Catalog now supports business context and semantic search (Preview), AWS What’s New (June 17, 2026). https://aws.amazon.com/about-aws/whats-new/2026/06/aws-glue-data-catalog/
- Amazon Q Business availability change, AWS Documentation. https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/qbusiness-availability-change.html
- Amazon Q Developer pricing, AWS. https://aws.amazon.com/q/developer/pricing
- Amazon Q is now generally available in Amazon QuickSight, AWS Business Intelligence Blog (April 30, 2024). https://aws.amazon.com/blogs/business-intelligence/amazon-q-is-now-generally-available-in-amazon-quicksight-bringing-generative-bi-capabilities-to-the-entire-organization/
- AWS launches Amazon Quick, Connect family of business apps, OpenAI managed agents, Constellation Research, Larry Dignan (April 28, 2026). https://www.constellationr.com/insights/news/aws-launches-amazon-quick-connect-family-business-apps-openai-managed-agents
- Reimagine the way you work with AI agents in Amazon Quick Suite, AWS Blog. https://aws.amazon.com/blogs/aws/reimagine-the-way-you-work-with-ai-agents-in-amazon-quick-suite/
- Amazon Q in QuickSight simplifies data exploration with Generative BI capabilities (Preview), AWS What’s New (November 28, 2023). https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-q-quicksight-data-exploration-generative-bi-capabilities-preview
- New – Amazon QuickSight Q Answers Natural-Language Questions About Business Data, AWS News Blog (December 1, 2020). https://aws.amazon.com/blogs/aws/amazon-quicksight-q-to-answer-ad-hoc-business-questions/
- Introducing catalog federation for Apache Iceberg tables in the AWS Glue Data Catalog, AWS Big Data Blog (November 26, 2025). https://aws.amazon.com/blogs/big-data/introducing-catalog-federation-for-apache-iceberg-tables-in-the-aws-glue-data-catalog/
