← Platform Foundations

▶ Play from here · 224 min

Starts this lesson and continues through 30 more to the end of the course.

The rename, and the three live doc trees

Why a naming lesson is the first lesson

Because you are going to spend the next year reading documentation, searching for error messages, and copying commands — and right now the name in the search box and the name in the command are different words.

That isn't a trivia problem. It's a "why does this Stack Overflow answer not match my console" problem, several times a week, until you have the mapping straight.

What happened

On October 9, 2025, AWS announced that Amazon QuickSight was becoming Amazon Quick Suite (AWS Business Intelligence Blog).

The product grew a set of AI capabilities around the BI tool, and the BI tool became one feature among several:

(All quoted from What is Amazon Quick?, verified 2026-08-09.)

Everything in this training track other than Q9 is about Quick Sight — the BI feature. When someone says "we use QuickSight", they almost always mean Quick Sight specifically, not the suite.

Naming inconsistency #1: is it "Quick" or "Quick Suite"?

The announcement blog says Amazon Quick Suite. The user guide's own overview page is titled "What is Amazon Quick?" and opens "Amazon Quick is an AI-powered service…". The AWS General Reference quota page is titled "Amazon Quick Sight".

I am not going to pretend one of those is authoritative. In practice:

• "Quick Suite" — the marketing/announcement name, and what most humans say
• "Quick" — what the current documentation calls the service
• "Quick Sight" — the BI feature, two words, which is the bit you care about

⚠️ Note the space. "Quick Sight" (two words, the current feature) is not "QuickSight" (one word, the old product, and still the API namespace). The one-word form is not obsolete — it's just moved from being the product name to being the identifier.

Naming inconsistency #2: three live documentation trees

This is the finding that will actually cost you time. Verified 2026-08-09, all three of these render real content:

These are not redirects. All three respond. And pages in one tree link into the others mid-sentence — the signup page in /quick/ links to /quicksuite/ for standalone signup and to /quicksight/ for IAM policy examples, in the same paragraph.

What this means for you, practically:

1. A bookmarked doc URL is not currently a stable reference. Record the page title and the date you read it, not just the link.
2. Two colleagues can be reading different versions of "the same page" and both be looking at current AWS documentation. When you disagree about behaviour, compare page titles and paths before arguing about facts.
3. When you cite documentation to AWS Support, paste the full URL, because "the data source quotas page" is now ambiguous.
4. Search results are a lottery between the trees. If a page looks stale, try swapping the path segment.

This course records a verifiedOn date and the exact URL fetched on every lesson for exactly this reason.

What did not change

This is the reassuring half, and AWS is unusually direct about it:

"All existing QuickSight APIs, SDKs, and integrations continue to work without changes."

Concretely, every one of these is unchanged and still spelled quicksight:

⚠️ Writing aws quick ... is a defect, not a modernisation. There is no such command. The same goes for quick:* IAM actions and arn:aws:quick:... — none of these exist.

The blog is explicit that the change is presentational: existing dashboards, datasets, analyses, data connectivity, security controls and user permissions all continue unchanged, and no data is migrated.

The working rule

Search in "Quick". Write in quicksight.

When you're reading — docs, console, release notes — expect "Quick" and "Quick Sight". When you're writing anything a machine will parse — CLI, IAM, Terraform, CloudFormation, ARNs, log filters — write quicksight.

Applied to a real task, finding out why a refresh failed:

# You searched the docs for "Quick Sight ingestion errors".
# You type this:
aws quicksight list-ingestions \
  --aws-account-id 111122223333 \
  --data-set-id sales-fact-v3 \
  --region us-east-1

Both names, one task, no contradiction.

Two ways to get an account, and they are not the same product

A detail that catches people evaluating the product: there are two entirely different signup paths.

(Quoted from What is Amazon Quick?.)

⚠️ If a colleague says "I tried it and it was free", check which one they used. A standalone account is not the thing you'll be running in production, and evaluating on it will teach you very little about VPC connectivity, row-level security, or SPICE capacity — none of which are that product's concerns. Everything in this track assumes the AWS-provisioned path.

Signing up through AWS also gets you a trial: "When you first sign up for Amazon Quick, you get a free trial subscription for twenty-five users for 30 days." (Signing up through the AWS Console)

Check yourself

1. A tutorial tells you to run aws quick describe-dashboard. What's wrong?
2. You and a colleague are reading "the data sources page" and disagree about the content. What's the first thing to establish?
3. Someone says "we're on QuickSight, not Quick Sight — should we migrate?" What's your answer?
4. A vendor demo was built on an account signed up at aws.com/quick. Name two things you can't conclude from it.
5. Why does this course record a URL and a date on every factual claim?

Answers

1. There is no aws quick command. The CLI is aws quicksight; the rename didn't touch the API, ARNs, IAM actions, or the service endpoint.
2. Which of the three live documentation trees each of you is on — /quicksight/latest/user/, /quick/latest/userguide/, or /quicksuite/latest/userguide/. Compare full URLs, not page names.
3. There is nothing to migrate. It's a rename of the console and docs; AWS states existing APIs, SDKs and integrations continue to work without changes, and no data is moved.
4. You can't conclude anything about VPC/on-premises connectivity, row-level or column-level security, SPICE capacity management, embedding, or per-user subscription cost. The standalone product is a different offering with a different identity model.
5. Because with three doc trees live and a rename still settling, a bare link is not a stable reference. The title plus the date is what makes a claim checkable later.

Teaching this section

• Open by writing both names on the board and asking which one goes in a Terraform file. The split — read "Quick", write quicksight — is the whole lesson and it takes thirty seconds to transmit.
• Demo: open the same conceptual page from two of the three doc trees, side by side. People assume you've made a mistake until they read the URLs. That moment is worth more than the table.
• Good discussion: "How should we cite documentation in our own runbooks, given this?" Get to a team convention — full URL plus retrieval date — and write it down.
• Watch for: learners "correcting" quicksight to quick in code during later labs, believing they're being current. Head it off here.
• Timing: 20 min presented, 10 discussion.