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 October 9, 2025, then shortened again to Amazon Quick in 2026, and Amazon Q Business itself closed to new customers on July 31, 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 July 31, 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, why AWS’s own users are confused about the naming, 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 October 9, 2025, then shortened to Amazon Quick in 2026 |
| Amazon Q Business status | Closed to new customers July 31, 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?
Permalink to “What is Amazon Q, and is it one product or several?”Amazon Q is AWS’s umbrella brand for a set of separate generative AI assistants, each built into a specific AWS service rather than sold as one package. AWS’s own documentation describes it this way: according to AWS’s “What is Amazon Q?” guide, Amazon Q is a generative AI-powered assistant available across several AWS surfaces, each scoped to a different job. Wikipedia’s entry on Amazon Q is a general reference point for the same product family, though it leans on the singular “chatbot” framing rather than spelling out the per-service split the way AWS’s own docs do.
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, just never as one purchasable unit you could buy together. 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?
Permalink to “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)
Permalink to “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)
Permalink to “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. Third-party analysis at InSearch, cross-checked against AWS’s own docs, puts it plainly: “This is not a rename or a console refresh. Quick is a different and considerably wider product.” QuickSight’s BI capability continues inside Quick Suite as a component AWS calls “Quick Sight,” with a space.
Amazon Quick Suite to Amazon Quick (2026 shorthand)
Permalink to “Amazon Quick Suite to Amazon Quick (2026 shorthand)”The name shortened again in 2026, from Amazon Quick Suite to simply Amazon Quick. A comparison published the same week as the rename already had to spell out, entity by entity, how Amazon Quick Suite differed from Amazon Q, the exact confusion AWS’s own community forum surfaces below.
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” |
| 2026 | Amazon Quick | “Amazon Quick Suite” shortened to “Amazon Quick” per AWS community moderator confirmation |
| July 31, 2026 | Amazon Q Business closed to new customers | Existing customers keep patches; no new signups; migration path points to Amazon Quick |
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
Permalink to “Amazon 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.
What it isn’t matters just as much as what it is. It doesn’t replace or restructure the Glue Data Catalog; it’s a chat and code-generation layer that reads from a catalog it doesn’t govern. Atlan’s breakdown of AWS Glue Data Catalog’s limitations covers the gaps in built-in business glossaries that this Q assistant doesn’t touch, because it was never built to. A broader data catalog for AI fills those gaps, since Q-in-Glue only ever sees the AWS slice of an estate. 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.
Why is there a forum thread asking what this AWS product is even called?
Permalink to “Why is there a forum thread asking what this AWS product is even called?”The naming confusion isn’t an outside narrative. AWS’s own QuickSight and Quick user community has an open thread from a long-time user asking exactly that question.
A long-time QuickSight user posted to the AWS Quick Community forum with the thread title “What’s this service even called?”, writing: “I’ve used QS for a number of years, where it has always been QuickSight. However, I’ve seen it was rebranded to Quick Suite in the last few months, and in more recent times, simply just to Quick.” An AWS moderator confirmed the whole chain in one reply: “Quick Sight was rebranded to Quick Suite a few months ago when they rolled out additional AI features… Very recently, the name Quick Suite was changed to simply Quick,” adding that “Quick Sight still exists as the business intelligence component, but it now lives within Quick.”
That thread isn’t a one-off. A second, independent thread on AWS re:Post asks the identical question, “Quick or Quick Suite still?” Two separate corners of AWS’s own user community, independently confused by the same rename.
Amazon Q Business’s closure to new customers, and the migration path to Amazon Quick
Permalink to “Amazon Q Business’s closure to new customers, and the migration path to Amazon Quick”Amazon Q Business stopped accepting new customers on July 31, 2026, and AWS is positioning Amazon Quick as where those customers, and their use cases, go next.
What happens to existing Amazon Q Business customers
Permalink to “What happens to existing Amazon Q Business customers”AWS’s own availability-change documentation confirms existing Q Business customers keep bug fixes and security patches, but no new feature requests will ship, and AWS hasn’t published a forced shutdown date. Third-party framing at InSearch, cross-checked against that AWS doc, describes Quick Suite as “the next evolution of Amazon Q Business.”
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?
Permalink to “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. Amazon Q Business covers enterprise search and chat over connected documents and apps, and it closed to new customers on July 31, 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 |
| Amazon Q Business | Enterprise search and chat over connected apps and documents | Q Business console | Closed to new customers July 31, 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
Permalink to “How 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, which has no built-in business glossary and covers only the AWS slice of an estate.
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
Permalink to “What AWS’s renamed AI layer means for your context strategy”Amazon Q was never a single bundle spanning QuickSight and Glue. It’s AWS’s brand for separate assistants living inside separate services, and half of the original story has already changed names twice since 2024. QuickSight is now Amazon Quick, Amazon Q Business closed its doors to new signups on July 31, 2026, and the one durable piece, AWS Glue Data Catalog, is also the one AWS itself documents as limited to its own slice of the estate.
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
Permalink to “FAQs about Amazon Q, QuickSight, and Glue”1. What is the difference between Amazon Q and Amazon QuickSight?
Permalink to “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 later renamed Amazon Quick Suite in October 2025, then Amazon Quick in 2026, 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?
Permalink to “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?
Permalink to “3. Is Amazon QuickSight still called QuickSight, or is it Quick Suite or Amazon Quick now?”As of 2026, it’s Amazon Quick. AWS renamed QuickSight to Amazon Quick Suite on October 9, 2025, then shortened that to Amazon Quick within months. QuickSight’s original BI capability still exists as a component called Quick Sight living inside Amazon Quick, confirmed directly by an AWS moderator responding to user confusion on the Quick community forum.
4. Is Amazon Q Business shutting down?
Permalink to “4. Is Amazon Q Business shutting down?”Not immediately, but it closed to new customers on July 31, 2026. Existing customers keep bug fixes and security patches, with no new feature investment and no publicly announced forced shutdown date. AWS positions Amazon Quick as the next evolution of Q Business, and that’s where new use cases and new customers are being directed.
5. Does Amazon Q use the AWS Glue Data Catalog?
Permalink to “5. Does Amazon Q use the AWS Glue Data Catalog?”The Amazon Q assistant embedded in AWS Glue does. It’s documented to answer questions and generate scripts that reference the Glue Data Catalog. But the Data Catalog itself is a separate, unchanged AWS service; Amazon Q doesn’t modify, replace, or restructure it. It’s a chat and code-generation layer that reads from the catalog, not a catalog feature itself.
6. What’s the difference between Amazon Q Developer, Amazon Q Business, and Amazon Q in QuickSight or Quick?
Permalink to “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. Q Business handles enterprise search and chat over connected apps and documents, and it closed to new customers on July 31, 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?
Permalink to “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, later shortened to Amazon Quick in 2026, and it’s still active today.
Sources
Permalink to “Sources”- What is Amazon Q?, AWS Documentation. https://docs.aws.amazon.com/amazonq/latest/aws-builder-use-ug/what-is.html
- Amazon Q, Wikipedia. https://en.wikipedia.org/wiki/Amazon_Q
- 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/
- Amazon Q Business vs Amazon Quick Suite: What Actually Changes, InSearch. https://insearch.ai/blog/amazon-q-business-vs-amazon-quick-suite
- Amazon Quick Suite vs Amazon Q: Understanding AWS’s AI Offerings, Kevin Xu (October 20, 2025). https://jkevinxu.github.io/github-blog/2025/10/20/amazon-quick-suite-vs-amazon-q.html
- 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/
- “What’s this service even called?”, AWS Quick Community forum. https://community.amazonquicksight.com/t/whats-this-service-even-called/51634
- “Quick or Quick Suite still?”, AWS re:Post. https://repost.aws/questions/QUCKGv0SwIR32EEellSgPhIw/quick-or-quick-suite-still
- Amazon Q Business availability change, AWS Documentation. https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/qbusiness-availability-change.html
- Amazon Q Business Closed to New Customers on July 31, 2026, InSearch. https://insearch.ai/blog/amazon-q-business-closing-to-new-customers
- 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/
