Cost Explorer shows spend. It does not find idle AWS.
Cost Explorer, Compute Optimizer, Cost Optimization Hub, and Budgets show AWS spend. They do not name the idle resource. A read-only scan does.
read article→Notes for the people who own the AWS bill: platform leads, FinOps, CTOs who want a digest they can forward. What Cost Explorer misses. What a read-only scan actually names.
A new AWS scan only shows what is idle now. The finding ledger keeps each resource until a later complete scan says it cleared. That is how realized savings get counted.
Startup and above can register, configure, and trigger read-only AWS scans from the public API. The IAM role still has to exist in each account before a scan runs.
Navi is the unusd.cloud assistant grounded in your latest AWS scan. It ranks remediations, cites resource IDs, and does not change a single resource in your account.
unusd.cloud posts the executive AWS cost digest to a Telegram Channel you own. Spend, waste, this week's actions. Per-account scans stay on email, Slack, or Teams.
Month-end AWS bills are late on purpose. unusd.cloud flags spend that breaks your usual pattern, then forecasts end of month and end of year from the same scans.
Dev bastions, CI, and non-prod RDS often sit idle all night and weekend. unusd.cloud flags working-hours AWS resources and estimates what a stop schedule would save.
unusd.cloud is on AWS Marketplace. Subscribe against your existing AWS invoice, skip a new vendor setup, and ask for a private offer when procurement needs it.
AWS EKS extended support is six times standard cluster pricing. RDS, OpenSearch, and ElastiCache have the same trap. How to see it before it hits the bill.
Small AWS charges (NAT, Elastic IPs, snapshots, VPC endpoints) look harmless alone. Across accounts and regions they become the line finance cannot explain.
You can hunt idle EC2, RDS, and EBS with CloudWatch and the AWS CLI. You will miss a region. Here are the commands, and why teams stop doing it by hand.
Lambda CPU scales with memory, so a bigger function can finish cheaper. That trick does not help functions nobody invokes. How to tell the two apart.
Horror-story AWS bills are real. Most of the ones you can prevent are idle resources and zombie accounts, not account takeovers. How to catch them early.
Unused AWS resources do not show up in standup. They show up on the invoice. How read-only scans find idle EC2, detached EBS, and forgotten RDS before finance does.