Amazon Quick Suite History (2026): From QuickSight Q and Q Business to Quick — What Deprecated and What to Buy
Quick summary: 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.
Key Takeaways
- 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 — an agentic workspace for research, BI, and automation
- The public product surface is Amazon 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
Table of Contents
On October 2025, AWS made Amazon Quick Suite generally available — an agentic workspace for research, BI, and automation. The public product surface is Amazon 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.
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/:lineage-successor-matrix.md,q-business-to-quick-migration-checklist.md,lineage-timeline.csv, and the draw.io diagramlineage-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” and 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.
| Service | Cutoff | Successor for net-new | Migration note |
|---|---|---|---|
| Amazon Q Business | July 30/31, 2026 | Amazon Quick Suite | BYOI — 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)
- 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).
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.
How this differs from posts we already published
| Existing asset | Role | This post |
|---|---|---|
| Lifecycle June 2026 | Broad maintenance/sunset matrix | Deep Quick lineage + migration checklist |
| AgentCore vs Quick | TCO / category split | History + deprecated predecessors |
| Q Business SharePoint/S3 how-to | Connector setup (legacy path) | When to stop net-new Q Business and use Quick |
| QuickSight Generative BI | BI feature guide | Where QuickSight sits in the Quick Suite story |
| Quick Suite service page | Consulting offer | Field history for architects / procurement |
What to do this week
- Search RFPs and architecture ADRs for “Q Business,” “Kendra,” and “QuickSight Q” — rewrite net-new language to Quick Suite / Quick Index / Bedrock KB.
- If you already run Q Business — schedule BYOI attach + 5 golden ACL queries; do not open a second net-new Q Business account.
- If you only need coding assist — stay on Q Developer; ignore Quick seat math.
- If you need customer-facing agents — evaluate AgentCore, not Quick seats.
- Download the successor matrix 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 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 and Amazon Q for Business (existing-tenant path).
AWS Cloud Architect & AI Expert
AWS-certified cloud architect and AI expert with deep expertise in cloud migrations, cost optimization, and generative AI on AWS.
