All cheat sheets
Operational Efficiencycheat sheet

QuickSight Reader Pricing

QuickSight readers cost $0.30 per 30-minute session, capped at $5/user/month — light users cost pennies, heavy users self-cap. It's what makes company-wide BI cost hundreds instead of the $30–70/seat that traditional BI charges.

Last reviewed: July 11, 2026

Prefer step by step? Take the guided QuickSight Reader Pricing walkthrough — free, anonymous, interactive.Have an AI assistant? Jump to the copy-paste audit prompt at the bottom of this sheet.

TL;DR: QuickSight charges viewers $0.30 per 30-minute session, capped at $5/user/month — so the exec who checks one dashboard a quarter costs $0.30 and the analyst who lives in it self-caps at $5. That shape is why you can hand BI to 400 people for ~$400/month while traditional per-seat tools would charge $12k–20k. The levers: don't over-grant Author seats ($18–24/month each), watch email reports (each delivery bills a session per recipient), and switch to flat per-user pricing only when most readers hit the cap anyway.

The numbers

  • Readers: $0.30/session (30-min window, per user not per dashboard), $5/month cap (~16 sessions) — or flat $5/user if you choose per-user mode
  • Authors: $18/month (Enterprise annual) or $24 (monthly)
  • Field example: 380 sales reps + 4 authors = ~$816/month total (24 capped users, a long tail at $0.30–1.80, 80 at zero) vs ~$26,000/month at Tableau-style seats; adding 200 more occasional viewers later cost ~$100/month
  • Counter-example: 50 analysts, 47 hitting the cap — per-session ≈ per-user ($240 vs $250), so they switched to flat per-user purely for predictability

Do this

  1. Default new deployments to Enterprise + per-session readers — it's the cheapest model for ~95% of orgs because usage is always long-tailed. Don't pre-buy capacity pricing without proven volume (>~5,000 sessions/month is embedded-analytics territory).

  2. Grant Reader, not Author. Authoring means building analyses/datasets; interacting with filters on a published dashboard doesn't need it. A sane ratio is ~1 author per 30–50 readers; annual commitment saves 25% on the authors you do need.

  3. Run the quarterly cull: inactive 90+ days → remove; Authors with no content edits in 60 days → downgrade to Reader (they still see everything). A 1,000-user deployment typically has 20–40% cleanup-eligible.

  4. Audit email-report subscriptions — a daily report to 100 non-visiting recipients ≈ 100 sessions/day ≈ $900/month. Cancel the ones nobody opens (Enterprise tracks open rates).

  5. Re-check the model at month 6: >70% of readers capped → flip to per-user for a flat, predictable line (same cost, less accounting); otherwise stay per-session.

Gotchas

  • Sessions are generous but real: the 30-minute window starts at open and isn't extended by interaction; multiple dashboards share one session; a tab left open all day is one session at open.
  • The cap doesn't roll over month to month.
  • Q (natural-language queries), ML insights, and paginated reports bill separately — enabling Q adds ~$250/month minimum.
  • Embedded/customer-facing dashboards are a different pricing universe (no per-user cap for anonymous users; capacity pricing at volume) — don't size external products on internal reader math.
  • Session counters lag a few hours; don't debug billing with real-time expectations.

Skip this if

  • Every reader is a full-time analyst — flat per-user pricing is identical in cost and simpler to administer.
  • You're embedding at high volume — negotiate capacity pricing, or consider pre-rendered reports for millions of views.
  • Your bigger QuickSight line is the in-memory engine — that's SPICE capacity, the usual second-largest item.

Run this audit with your AI assistant

Paste this into Claude, ChatGPT, or any agent that can run the AWS CLI with read-only credentials. It audits your account for exactly the waste this sheet describes — and changes nothing.

You are auditing a QuickSight deployment's user and pricing setup. Use
the AWS CLI with READ-ONLY credentials. Do not create, modify, or
delete anything.

1. Inventory users: aws quicksight list-users --aws-account-id <acct>
   --namespace default — count by Role (ADMIN/AUTHOR/READER) and note
   Active status. Authors bill $18–24/user/month; readers per-session
   ($0.30/session, $5/mo cap) or flat $5/user depending on account
   setting.
2. Findings:
   a. Author over-grants: authors who plausibly only view (can't
      verify authoring activity via CLI — flag for console check of
      last-created content; anyone not authoring in 60 days →
      downgrade to Reader, saves $18–24/mo each).
   b. Inactive users (90+ days) — readers cost ~$0 idle but authors
      bill regardless; list author removals first.
   c. Per-session vs per-user model fit: if usage data (console →
      Manage QuickSight → usage) shows >70–80% of readers hitting the
      $5 cap, recommend flat per-user for admin simplicity; below
      that, per-session stays cheaper.
   d. Email-report subscriptions: each delivery = a session per
      recipient; large daily distributions can dominate the bill —
      flag for console review.
3. Cost model: current estimated $/mo (authors × rate + reader
   sessions) vs tuned setup.

Report: user counts by role, author-downgrade candidates, model
recommendation with the math, and the quarterly cleanup checklist. Do
NOT change any user or setting.
Works with any assistant that can run shell commands.

Want the guided version?

The QuickSight Reader Pricing walkthrough covers this topic interactively — it asks about your setup, branches to what’s relevant, and quizzes you on the tricky parts. Free and anonymous.

Start the walkthrough

More Operational Efficiency cheat sheets

AWS Config Resource Exclusion

AWS Config bills ~$0.003 per configuration item, and the 'record everything' default meters every ENI and Lambda-version change your account churns through. Excluding high-churn, zero-audit-value resource types cuts most Config bills 40–70%.

AWS License Manager

Windows EC2 costs ~2× Linux; SQL Server Enterprise adds $4–5/hour on top. If you already own those licenses under Software Assurance, BYOL removes the AWS markup — and License Manager is the free tracking layer that makes it audit-safe.

AWS Resource Explorer

Free, cross-region, cross-account search for everything in your AWS estate — the fastest way to surface the orphaned volumes, unassociated Elastic IPs, forgotten NAT Gateways, and idle SageMaker endpoints that accumulate in any account older than two years.

CloudWatch Logs Infrequent Access

The IA log class halves both ingestion (~$0.25/GB) and storage (~$0.015/GB-month) for write-and-forget log groups — but silently disables metric filters, subscription filters, and Live Tail. Know the disable list before you move anything.