--- title: Amazon Quick Suite History (2026): From QuickSight Q and Q Business to Quick — What Deprecated and What to Buy description: Quick Suite GA October 2025; Q Business and Kendra freeze new customers after July 30, 2026. A 420-seat professional-services firm paused a $38K/year Kendra quote and cut evaluation from 9 weeks to 3 by starting on Quick instead. url: https://www.factualminds.com/blog/amazon-quick-suite-history-q-business-kendra-migration-2026/ datePublished: 2026-07-10T00:00:00.000Z dateModified: 2026-07-10T00:00:00.000Z author: palaniappan-p category: Generative AI tags: amazon-quick, amazon-quick-suite, amazon-q-business, amazon-kendra, amazon-quicksight, generative-ai, aws-lifecycle --- # Amazon Quick Suite History (2026): From QuickSight Q and Q Business to Quick — What Deprecated and What to Buy > Quick Suite GA October 2025; Q Business and Kendra freeze new customers after July 30, 2026. A 420-seat professional-services firm paused a $38K/year Kendra quote and cut evaluation from 9 weeks to 3 by starting on Quick instead. On **October 2025**, AWS made [Amazon Quick Suite generally available](https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-quick-suite-agentic-ai-powered-workspace/) — an agentic workspace for research, BI, and automation. The public product surface is [Amazon Quick](https://aws.amazon.com/quick/). On **June 30, 2026**, AWS put **Amazon Q Business** and **Amazon Kendra** into maintenance for **new** customers after **July 30, 2026**, with Quick Suite as the workforce successor. In **June 2026**, Quick also shipped [autonomous agents, multi-dataset analytics, and a redesigned activity feed](https://aws.amazon.com/about-aws/whats-new/2026/06/amazon-quick/). **Engagement shape (July 2026):** a professional-services firm (~420 knowledge workers, SharePoint + Confluence + ~2.1M indexed objects, prior GenAI pilot on a single Q Business app). Procurement had a **$38K/year** Kendra Enterprise line item in flight when the lifecycle notice landed. They paused Kendra, opened a Quick Suite trial, and finished a go/no-go in **3 weeks instead of a planned 9-week** dual-track (Kendra + Q Business) evaluation — **~6 weeks of vendor diligence avoided** before signing a multi-year search SKU that would have entered maintenance mid-procurement. This post is the **product history + successor map**. It is not the AgentCore vs Quick TCO guide, not the June lifecycle matrix dump, and not a QuickSight embedding how-to. > **Reproduce this** — Clone the artifacts under [`examples/architecture-blog-2026/amazon-quick-suite/`](/examples/architecture-blog-2026/amazon-quick-suite/): [`lineage-successor-matrix.md`](/examples/architecture-blog-2026/amazon-quick-suite/lineage-successor-matrix.md), [`q-business-to-quick-migration-checklist.md`](/examples/architecture-blog-2026/amazon-quick-suite/q-business-to-quick-migration-checklist.md), [`lineage-timeline.csv`](/examples/architecture-blog-2026/amazon-quick-suite/lineage-timeline.csv), and the draw.io diagram [`lineage-2026.drawio`](/examples/architecture-blog-2026/amazon-quick-suite/lineage-2026.drawio). --- ## Product history (what became Amazon Quick) | Era | Product | What it was | What happened | | ------------ | --------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | 2021–2023 | **QuickSight Q** | Natural-language Q&A add-on on QuickSight | Superseded by Amazon Q in QuickSight (Generative BI) | | ~2024 | **Amazon Q in QuickSight** | Generative BI for Authors/Readers | Folded into **Quick Sight** inside Quick Suite; existing dashboards stay | | 2024–2025 | **Amazon Q Business** | Workforce chat + enterprise index + connectors | **Next evolution = Quick Suite**; new customers freeze after July 30/31, 2026 | | Pre-2026 | **Amazon Kendra** | Managed enterprise search | Maintenance for new customers; successor = **Quick Index** or **Bedrock Knowledge Bases** | | **Oct 2025** | **Amazon Quick Suite** | Agentic workspace: Index, Research, Sight, Flows, Automate, Spaces | **Net-new default** for employee AI | | Jan–Jun 2026 | **Amazon Quick** expansions | 3P agents/actions (Jan), New Relic agents (May), autonomous agents + multi-dataset analytics (Jun) | Same product family; deeper automation | AWS’s own framing: Quick Suite is “[the next evolution of Amazon Q Business](https://aws.amazon.com/q/business/connectors/)” and QuickSight “[evolves to Amazon Quick Suite](https://aws.amazon.com/blogs/business-intelligence/reimagine-business-intelligence-amazon-quicksight-evolves-to-amazon-quick-suite/)” without requiring a data migration for existing BI assets. > **Opinionated take** — Buy **Quick Suite** for employees + company data + actions. Buy **Bedrock AgentCore** for customer-facing or embedded agents you own. Keep **Q Developer** for IDE coding. Do not collapse those three into one RFP line item. --- ## What entered maintenance because of this shift These are **not sunsets** for existing tenants. They are **new-customer freezes** (maintenance) with named successors. Full batch context: [AWS service lifecycle updates — June 2026](/blog/aws-service-lifecycle-updates-june-2026/). | Service | Cutoff | Successor for net-new | Migration note | | ----------------------------------- | ---------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Amazon Q Business** | July 30/31, 2026 | **Amazon Quick Suite** | [BYOI](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/qbusiness-availability-change.html) — attach existing Q index; then adopt Research / Flows / Spaces | | **Amazon Kendra** | July 30, 2026 | **Quick Index** (workforce) or **Bedrock Knowledge Bases** (app RAG) | Stop net-new Kendra quotes in RFPs | | **Bedrock Agents → Agents Classic** | July 30, 2026 | **Bedrock AgentCore** | Parallel lifecycle event — **not** replaced by Quick | **QuickSight itself is not deprecated.** Authors keep dashboards, SPICE, embedding APIs, and compliance postures; the UI brand moves toward Quick Sight inside the suite. ### What is _not_ deprecated by Amazon Quick - **Amazon Q Developer** / Kiro CLI — coding assistants - **Bedrock AgentCore** — custom agent runtime (see [AgentCore vs Quick decision guide](/blog/aws-bedrock-agentcore-vs-amazon-q-enterprise-decision-guide-2026/)) - Existing **Q Business** and **Kendra** tenants — supported; freeze is for _new_ customers --- ## Migration path: Q Business → Quick (BYOI first) AWS documents a phased path: attach the existing index (**Bring Your Own Index**), move users onto Quick capabilities, then optionally re-home connectors onto Quick Index over time. Anonymous access and custom API embeddings need **AWS Support** — do not assume BYOI covers them ([availability change](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/qbusiness-availability-change.html)). > **What broke** — Week 2 of a BYOI pilot: chat answers looked fine in the Quick UI, but a SharePoint ACL edge case still returned a restricted folder for a contractor Identity Center group. Caught only when we replayed **5 golden queries** with expected deny/allow. Fix: re-validate identity propagation and document ACLs before expanding beyond the pilot cohort — do not treat “index attached” as “permissions proven.” Use the checklist: [`q-business-to-quick-migration-checklist.md`](/examples/architecture-blog-2026/amazon-quick-suite/q-business-to-quick-migration-checklist.md). --- ## How this differs from posts we already published | Existing asset | Role | This post | | --------------------------------------------------------------------------------------------- | ------------------------------- | ---------------------------------------------- | | [Lifecycle June 2026](/blog/aws-service-lifecycle-updates-june-2026/) | Broad maintenance/sunset matrix | Deep Quick **lineage** + migration checklist | | [AgentCore vs Quick](/blog/aws-bedrock-agentcore-vs-amazon-q-enterprise-decision-guide-2026/) | TCO / category split | History + deprecated predecessors | | [Q Business SharePoint/S3 how-to](/blog/how-to-set-up-amazon-q-for-business-sharepoint-s3/) | Connector setup (legacy path) | When to stop net-new Q Business and use Quick | | [QuickSight Generative BI](/blog/amazon-q-quicksight-generative-bi/) | BI feature guide | Where QuickSight sits in the Quick Suite story | | [Quick Suite service page](/services/amazon-quick-suite/) | Consulting offer | Field history for architects / procurement | --- ## What to do this week 1. **Search RFPs and architecture ADRs** for “Q Business,” “Kendra,” and “QuickSight Q” — rewrite net-new language to Quick Suite / Quick Index / Bedrock KB. 2. **If you already run Q Business** — schedule BYOI attach + 5 golden ACL queries; do not open a second net-new Q Business account. 3. **If you only need coding assist** — stay on Q Developer; ignore Quick seat math. 4. **If you need customer-facing agents** — evaluate AgentCore, not Quick seats. 5. **Download** the [successor matrix](/examples/architecture-blog-2026/amazon-quick-suite/lineage-successor-matrix.md) and paste it into the next architecture review. --- ## What this post doesn’t cover - Per-region GA matrix and Identity Center org setup screenshots - Full Quick Flows / Automate authoring patterns - QuickSight embedding for SaaS (see existing embedding posts) - First-party seat-by-seat TCO (use the [AgentCore vs Quick guide](/blog/aws-bedrock-agentcore-vs-amazon-q-enterprise-decision-guide-2026/) for that benchmark) - Legal review of every compliance inheritance claim — verify against your AWS account team for FedRAMP boundary specifics For implementation help: [Amazon Quick Suite consulting](/services/amazon-quick-suite/) and [Amazon Q for Business](/services/amazon-q-for-business/) (existing-tenant path). ## FAQ ### Is Amazon Quick the same as Amazon Quick Suite? Amazon Quick is the product brand on aws.amazon.com/quick — the AI assistant / agentic workspace. Amazon Quick Suite is the enterprise workspace name AWS uses in docs and What’s New (Quick Index, Quick Research, Quick Sight, Quick Flows). Treat them as the same family for procurement; use Quick Suite language in architecture docs. ### When should we NOT migrate from Q Business to Quick yet? Stay on existing Q Business if you have anonymous-access or custom API embeddings without a Support-approved path — AWS tells those customers to contact Support. Also skip forcing Quick seats for high-volume customer-facing chat; that is usually Bedrock AgentCore, not Quick. ### Did Amazon QuickSight get deprecated? No. Dashboards, datasets, APIs, and compliance attestations stay. QuickSight evolves into the Quick Sight surface inside Quick Suite — in-place UI upgrade for existing customers, not a data migration. See the AWS BI blog on QuickSight → Quick Suite. ### Is Amazon Q Developer replaced by Quick? No. Q Developer (and Kiro CLI) remains the IDE / coding path. Quick is workforce research, BI, and automation — different buyer and different seat model. ### What replaces Amazon Kendra for net-new search? Workforce permission-aware search: Quick Index inside Quick Suite. Application-embedded RAG: Bedrock Knowledge Bases. Do not start net-new Kendra after the July 30, 2026 new-customer cutoff. ### What could go wrong in a Q Business → Quick migration? Assuming every Q Business API pattern maps 1:1; skipping ACL validation after BYOI; treating AgentCore and Quick as interchangeable; and leaving RFP language on Q Business / Kendra after the maintenance cutoff so procurement buys a dead SKU. --- *Source: https://www.factualminds.com/blog/amazon-quick-suite-history-q-business-kendra-migration-2026/*