In the previous subchapter, you learned how to view and control your costs with Cost Explorer and Budgets. Those tools show you the spending, but you have to decide what to optimize. What if AWS gave you specific recommendations on what to change to save and improve? That’s what Trusted Advisor and Compute Optimizer do: two automatic advisors that analyze your account and proactively tell you what to do.

The difference: from “seeing” to “advising”

Cost Explorer shows you the numbers; these tools go a step further and recommend actions:

Cost Explorer   → "you spend €450 on servers"        (informs you)
Trusted Advisor → "you have 3 almost idle servers,
                   turn them off and you'll save €200"   (advises you)

It’s the difference between a dashboard (which shows data) and an advisor (who tells you what to do with it).

Trusted Advisor: your account’s general advisor

AWS Trusted Advisor is like an automatic consultant that reviews your AWS account and gives you recommendations in several categories, not just costs. It analyzes your account and points out opportunities for improvement and issues:

Trusted Advisor reviews and recommends in these areas:
   💰 Cost optimization      (underutilized resources, savings...)
   🔒 Security              (insecure configurations)
   ⚡ Performance           (mis-sized resources)
   🛡️ Fault tolerance       (lack of redundancy, backups...)
   📊 Service limits        (you’re approaching an AWS limit)

Analogy: Trusted Advisor is like bringing in an expert inspector to review your house who, as they walk through, tells you: “this window doesn’t close properly (security)”, “you have a lightbulb wasting energy (cost)”, “you’re missing a smoke detector here (security/faults)”, “this outlet is overloaded (performance)”. It gives you a clear list of what to fix and why.

Examples of Trusted Advisor cost recommendations

  • “You have servers with very low usage → consider turning them off or downsizing.”
  • “You have reserved IP addresses not in use → you’re being charged for nothing, release them.”
  • “You have disks not attached to any server → they’re still costing you, delete them.”
  • “You could save by purchasing reserved capacity for these resources” (we’ll cover this in subchapter 25.4).

Each recommendation usually comes with the estimated savings, so you can prioritize.

Compute Optimizer: the sizing specialist

AWS Compute Optimizer is more specialized: it focuses on recommending the right size for your compute resources (EC2 servers, Lambdas, etc.). It analyzes how you actually use those resources (their CPU, memory, etc., over time, using CloudWatch data) and tells you if they are properly sized, oversized (too big, wasting money), or undersized (too small, running tight).

Compute Optimizer analyzes your server:
   "This 'large' server only uses 10% of its capacity.
    RECOMMENDATION: switch to a 'medium' one → save 50% without losing performance"

Analogy: Compute Optimizer is like an advisor who looks at your electricity bill and your habits and tells you: “you have a 10 kW contract but never go above 4; drop to 5 kW and you’ll pay much less without ever falling short.” It looks at your actual usage and adjusts the size to what you really need.

This size adjustment is so important it has its own name —rightsizing— and we dedicate the next entire subchapter (25.3) to it. Compute Optimizer is the tool that gives you those rightsizing recommendations with data.

Trusted Advisor vs Compute Optimizer

Trusted Advisor Compute Optimizer
Scope General: costs, security, performance, faults, limits Specialized in compute sizing (EC2, Lambda...)
Type of advice Varied (turn off resources, improve security...) Optimal size based on actual usage
Analogy General house inspector Contracted power advisor

They complement each other: Trusted Advisor gives you a broad view of improvements in many areas, and Compute Optimizer dives deep into the optimal sizing of your compute resources.

Real-world example: a company has been on AWS for a year without reviewing anything. They activate Trusted Advisor and get a list: 5 unused IPs (charging for nothing), 8 orphaned disks, 3 almost idle servers, and two security alerts. Then they check Compute Optimizer, which tells them half their servers are oversized and could use smaller sizes. By applying the recommendations, they reduce their bill by 35% without affecting service, and also improve their security. All thanks to automatic advisors they just had to look at.

How it fits into the cost strategy

Cost Explorer / Budgets (25.1)  → SEE and CONTROL spending
Trusted Advisor (this)          → BROAD RECOMMENDATIONS (costs, security...)
Compute Optimizer (this)        → OPTIMAL SIZE RECOMMENDATIONS (rightsizing)
        │
        ▼
   Rightsizing (25.3) → apply the size adjustment

First you see the spending, then you get recommendations, and then you act (starting with rightsizing in the next subchapter).

What you should remember

  • Cost Explorer and Budgets show and control spending; Trusted Advisor and Compute Optimizer go a step further and recommend specific actions. It’s moving from a dashboard to an advisor.
  • Trusted Advisor is a general automatic consultant that reviews your account and recommends improvements in costs, security, performance, fault tolerance, and limits (with estimated savings). Like an inspector walking through your house pointing out what to fix.
  • Compute Optimizer is specialized in recommending the right size for your compute resources based on their actual usage (detects oversized and undersized). Like a contracted power advisor.
  • They complement each other: Trusted Advisor gives a broad view, Compute Optimizer dives deep into sizing (rightsizing).
  • Applying their recommendations can greatly reduce your bill without affecting service, and also improve security and reliability.

In the next subchapter, we’ll dive deeper into the most direct savings technique these tools recommend: rightsizing (adjusting the size of resources to what you really need).

Cloud, AWS & Terraform — From Zero to Expert

Chapter 1 · What is cloud computing

Chapter 2 · The cloud market and major providers

Chapter 3 · Regions, availability zones and edge

Chapter 4 · Compute: EC2

Chapter 5 · Storage: S3

Chapter 6 · Networking: VPC

Chapter 7 · Identity and access: IAM

Chapter 8 · Managed databases

Chapter 9 · Why Infrastructure as Code

Chapter 10 · HCL: the Terraform language

Chapter 11 · Providers and state

Chapter 12 · Your first real infrastructure in Terraform

Chapter 13 · Load balancing and auto scaling

Chapter 14 · Serverless with Lambda

Chapter 15 · Messaging and events

Chapter 16 · Content delivery and DNS

Chapter 17 · Containers on AWS

Chapter 18 · Modules: reuse and composition

Chapter 19 · Workspaces and environment management

Chapter 20 · Remote backends and locking

Chapter 21 · Infrastructure testing

Chapter 22 · Terraform in CI/CD

Chapter 23 · Defense in depth

Chapter 24 · Observability: logs, metrics and traces

Chapter 25 · Cost optimization

Chapter 26 · High availability and disaster recovery

Chapter 27 · AWS Well-Architected Framework

Chapter 28 · Serverless architectures at scale

Chapter 29 · Data platforms on AWS

Chapter 30 · Multi-account and landing zones

Chapter 31 · Platform Engineering and Internal Developer Platform

Chapter 32 · Relevant AWS certifications

Chapter 33 · Projects to consolidate what you've learned

Chapter 34 · Resources and community

© Copyright 2024. All rights reserved