Amazon Quick Suite History (2026): From QuickSight Q and Q Business to Quick — What Deprecated and What to Buy

In 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, which avoided ~6 weeks of vendor diligence before signing a multi-year search SKU that would have entered maintenance mid-procurement.

This post covers the product history and successor map. AgentCore vs Quick TCO, the full June lifecycle matrix, and QuickSight embedding are covered in other posts (linked below).

Product history (what became Amazon Quick)

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.

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.

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 from Q Business to 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).

Use the checklist: q-business-to-quick-migration-checklist.md.

How this differs from posts we already published

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 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).

Frequently asked questions