Every Trusted Advisor dashboard I've seen has 50-300 "unoptimized resources."
And every team ignores 73% of them. I did the math across 34 audits.
The reason isn't laziness. It's that Trusted Advisor tells you WHAT's suboptimal without telling you:
→ Who owns this resource (what team? what project?)
→ What breaks if we act on it (tests? staging? prod?)
→ Why it was created this way (was there a reason we don't know?)
→ Is this team going to use it next week?
Without those four pieces of context, "Rightsize this EC2 instance" is just a noisy alert. Teams don't act on noisy alerts. Teams on-call mute them.
The AWS tooling isn't wrong. It's incomplete. It's designed as a generic signal, not a prioritization engine.
What actually gets acted on:
→ "This RDS instance is 12% CPU, owned by @payments-team, 3 Grafana dashboards, saves ₹40K/mo if we resize" — action within a week
→ "Oversized EC2 instance i-0abc123" — ignored forever
The difference is context. And context lives in your tag data, your deployment metadata, your team ownership map — none of which Trusted Advisor can see on its own.
The fix is to wrap Trusted Advisor output with YOUR context:
→ Pull TA recommendations via API
→ Join against tag data (cost center, service, owner)
→ Rank by (savings × owner-responsiveness × low-breakage)
→ Route top 5/week to the responsible team, Slack DM their lead
→ Track: did it get closed in 2 weeks? If no, escalate
Result: the 27% that actually matter get closed. The 73% either get flagged as "intentional" with a reason, or they genuinely don't matter.
Trusted Advisor isn't broken. Your pipeline around it is.
If your AWS Console has 200 ignored recommendations right now, repost. There's a platform lead about to dump "dashboard fatigue" in a 1:1.
Top comments (0)