Q0 — Platform Foundations

Why this module exists

Most people meet this product halfway through a project, inheriting an account somebody else set up, and spend the next year confused by decisions that were made in a five-minute signup wizard.

Three of those decisions are effectively permanent, two of them cost real money every month, and one of them determines whether row-level security is even available to you. None of them are obvious from the console afterwards.

This module is the map. It is deliberately the least exciting module in the track and the one that prevents the most wasted time.

The one idea to hold onto

The console name and the API name are different, permanently, and both are correct.

   WHAT YOU SEE                          WHAT YOU TYPE
   ┌──────────────────────────┐          ┌──────────────────────────────┐
   │ Amazon Quick             │          │ aws quicksight ...           │
   │   └─ Amazon Quick Sight  │   ←──→   │ quicksight:CreateIngestion   │
   │ docs: /quick/…           │          │ arn:aws:quicksight:…         │
   │ docs: /quicksuite/…      │          │ quicksight.<region>.amaz…    │
   └──────────────────────────┘          │ API version 2018-04-01       │
     renamed 2025-10-09                  └──────────────────────────────┘
                                           unchanged, deliberately

"Amazon Quick evolved from Amazon QuickSight. QuickSight continues as Amazon Quick Sight, a feature within Quick. All existing QuickSight APIs, SDKs, and integrations continue to work without changes." — What is Amazon Quick? (verified 2026-08-09)

If you internalise nothing else from Q0: search the docs for "Quick", write code that says quicksight.

What you'll be able to do

Say precisely what Amazon Quick, Quick Suite, and Quick Sight each refer to, and which name to use in which context.
Determine which edition an inherited account is on, and name the features that decision gates.
Explain the difference between an edition and a subscription, and why the docs currently describe both as current.
Choose an identity method at signup knowing which parts are hard to undo.
Say where an asset physically lives, and why the Region selector has caught you out already.
Draw the asset hierarchy from data source to dashboard, using both the console names and the API names.

Lessons

#	Lesson	Read	Listen
1	The rename, and the three live doc trees	22 min	9 min
2	Editions, subscriptions, and roles	26 min	9 min
3	Identity: the decisions you make once	26 min	8 min
4	Regions, and where your assets actually live	24 min	8 min
5	The asset hierarchy	26 min	8 min

Then: Cheat sheet · Lab · Quiz

A note on the docs

This module documents more AWS documentation inconsistency than any other in the track, because the October 2025 rename is still settling. The headline finding, verified 2026-08-09:

Three documentation trees are live simultaneously, serving overlapping content:

Path	Example page title
`docs.aws.amazon.com/quicksight/latest/user/`	"Connecting to data in Amazon Quick Sight"
`docs.aws.amazon.com/quick/latest/userguide/`	"Signing up through the AWS Console"
`docs.aws.amazon.com/quicksuite/latest/userguide/`	"Working with data sources in Amazon Quick Sight"

Pages in one tree link into the others, mid-paragraph, with no indication you're changing trees. This is not a redirect situation — all three render.

Consequence for you: a bookmarked doc page is not a stable reference right now, and a colleague's link may not be the page you think it is. Lesson 1 covers how to work with that instead of against it.

Facts verified 2026-08-09 against the pages cited in each lesson.

Keeps playing into the following modules — 79 min from here to the end of the course.