All cheat sheets
Cost Governancecheat sheet

AWS Cost Optimization Hub

The 2023 dashboard that finally puts every AWS cost recommendation — Compute Optimizer rightsizing, Trusted Advisor idle resources, Savings Plans/RI advice — on one sortable screen with dollar amounts. It prioritizes the work; it doesn't do it for you.

Last reviewed: July 14, 2026

TL;DR: For years, AWS cost recommendations lived in six consoles — Compute Optimizer for EC2 rightsizing, Trusted Advisor for idle resources, Cost Explorer for RI/SP advice. Cost Optimization Hub (Nov 2023) is AWS's first real attempt to put them all on one sortable screen with dollar amounts, scoped across your whole Organization. It's an aggregator, not a generator: it surfaces the underlying services' recommendations, with all their caveats intact, and it prioritizes the work but doesn't do it — you still need an external process to turn findings into tickets.

The numbers

  • Free — you pay only for the underlying services (Compute Optimizer is free; full Trusted Advisor cost checks need Business+ Support, ~$100/mo min).
  • Each recommendation carries estimated monthly savings, effort (low/med/high), risk, resource tags, and account ID — the killer view is sort by savings descending for a prioritized to-do list.
  • Setup: opt in (management account for Org scope), enable Compute Optimizer Org-wide, Cost Explorer with ~14 days history; wait 24–48 hours.
  • Field examples: a 200-account Org built a Lambda to push Hub findings to Jira and closed ~$80K/mo on a rolling basis (mostly SP coverage gaps + gp2→gp3); a 3-account startup found $1,400/mo, realized $1,100/mo ($13K/yr) in ~10 hours, on Basic Support.

Do this

  1. Enable it (30 min) from the management account at Organization scope, verify Compute Optimizer is enrolled Org-wide, then wait 24–48h.
  2. Sort by estimated savings descending, filter to Effort: Low — usually idle-resource deletions, Compute Savings Plan buys, and gp2→gp3 conversions you can act on this week.
  3. Group by account and tag to route each recommendation to the team that owns the resource.
  4. Run a 30-min weekly triage — mark in-flight items, open tickets for the rest, note disagreements (often burst workloads Compute Optimizer misreads); a healthy state is "top 5 are in-progress or intentionally deferred."
  5. Deep-dive in the source service before acting on a specific recommendation — the Hub is the dashboard, Compute Optimizer et al. are the workshop.

Gotchas

  • It aggregates, it doesn't sanitize — an EC2 rightsizing rec inherits Compute Optimizer's blind spots (e.g. it assumes CPU-bound without the CloudWatch Agent reporting memory, risking a dangerous downsize on memory-bound workloads).
  • No built-in workflow — it shows, it doesn't ticket; you need a Lambda or manual process to route findings, and refreshes lag 24–48h (a fix from yesterday may still show).
  • Trusted Advisor coverage is partial on Basic Support — Compute Optimizer recs come through regardless, but idle-resource cleanup checks are gated behind Business+.
  • Estimates are optimistic — SP savings assume current spend continues forever.
  • Each member account needs the source services enabled — Org scope alone shows "no data" for accounts where Compute Optimizer/Trusted Advisor are off.

Skip this if

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 an AWS account/Org's use of Cost Optimization Hub. Use
the AWS CLI with READ-ONLY credentials. Do not create, modify, or delete
anything — report findings and recommended (unapplied) fixes only.

1. Enablement: aws cost-optimization-hub list-enrollment-statuses — is it
   opted in, and at Organization scope? Confirm the source services are
   enabled: Compute Optimizer (compute-optimizer get-enrollment-status),
   Cost Explorer (>=14 days history), Trusted Advisor support tier.
2. Opportunity pull: aws cost-optimization-hub list-recommendations —
   sort by estimatedMonthlySavings desc; group by recommendationType,
   account, and (low) effort. Surface the top 10-20 by dollars.
3. Coverage gaps: flag member accounts showing "no data" (source
   services not enabled there) and Basic-Support accounts missing
   Trusted Advisor idle-resource checks.
4. Skepticism pass: note EC2 rightsizing recs likely affected by missing
   memory metrics (no CloudWatch Agent) — treat downsizes on memory-bound
   workloads with care.

Report a table: recommendation | source service | est. $/mo | effort |
account/tag | act now / verify / defer. Note the Hub doesn't ticket —
recommend an external routing process. Change nothing.
Works with any assistant that can run shell commands.

Want the guided version?

The AWS Cost Optimization Hub 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