Pillar review

Your AWS, Azure and Google Cloud accounts, sorted by Well-Architected pillars

What the platform already checks in your account, sorted by pillar: cost and rightsizing, plus posture and backups with the risk and compliance add-on. In the pillars with rules you see how many pass, how many have findings and how many could not be read, and in all of them, what is not checked.

It is not an official Well-Architected review from AWS, Microsoft or Google, does not replace one and gives no score.

  • 6

    pillars in the Pillars tab of every account

  • 3

    clouds: AWS, Azure and Google Cloud

  • 18

    backup and resilience checks across the three clouds

  • 14

    days: with an older scan, no rule shows as passing

Three frameworks

Each cloud has its own Well-Architected Framework

AWS, Google Cloud and Azure each publish their own framework. They share five pillars, and AWS and Google Cloud add sustainability. This is what each pillar is called in each framework:

Pillars of the AWS, Google Cloud and Azure Well-Architected Framework
Pillar AWS6 pillars Google Cloud6 pillars Azure5 pillars
Operational excellenceOperational ExcellenceOperational excellenceOperational Excellence
SecuritySecuritySecurity, privacy, and complianceSecurity
ReliabilityReliabilityReliabilityReliability
Performance efficiencyPerformance EfficiencyPerformance optimizationPerformance Efficiency
Cost optimizationCost OptimizationCost optimizationCost Optimization
SustainabilitySustainabilitySustainabilityNot a pillar of this framework

The tab uses the six pillars on the three clouds. On an Azure account, sustainability shows the same as on the others: as not checked.

Pillar by pillar

What each pillar counts and what is left out

Each card says where its counts come from, what the platform adds and what the pillar asks for that is not checked. The lists come from the same code as the tab in the app.

Where the counts come from

  • Posture rules (add-on)
  • Cost rules
  • Added by the platform
  • Not checked
  • Operational excellence

    No account rules: the platform covers it

    What the platform adds (depends on plan and add-on)

    • Deploy markers
    • Budget gate in CI
    • Terraform plan cost and security
    • Agent with approvals and undo
    • Critical change alerts

    What is not checked

    • Runbooks and procedures
    • Service level objectives (SLO) and error budgets
    • Incident postmortems
  • Security

    Posture rules, with the add-on

    What the platform adds (depends on plan and add-on)

    • Critical change alerts
    • Compliance questionnaires
    • Access reviews
    • Native tool findings

    What is not checked

    • WAF and DDoS protection
    • Containers and Kubernetes
    • Own vulnerability scanning (the cloud’s are imported)
    • Secrets in code
  • Reliability

    Backup and resilience rules, with the add-on

    What the platform adds (depends on plan and add-on)

    • Synthetic monitoring
    • Incidents and status pages
    • Map resilience lens

    What is not checked

    • Recovery tests
    • Recovery objectives (RTO and RPO)
    • Service quotas
    • Resources outside an AWS Backup plan
  • Performance efficiency

    Rightsizing rules, shared with cost

    What the platform adds (depends on plan and add-on)

    • Throttling and latency alerts

    What is not checked

    • Memory usage
    • Relational database instance sizing
    • Latency per workload
    • Moving to ARM instances
  • Cost optimization

    The cost rules of your plan

    What the platform adds (depends on plan and add-on)

    • Budgets and forecasts
    • Spend anomalies
    • Commitments (RI, Savings Plans, CUD)
    • Unit cost
    • AI spend

    What is not checked

    • Kubernetes allocation by namespace
    • Real-time anomalies
  • Sustainability

    Not checked

    What is not checked

    • Carbon footprint
    • Region carbon intensity
    • Workload energy efficiency

Counts only, with no score or percentage: the platform does not look at everything each pillar asks for. It is not an official Well-Architected review from AWS, Microsoft or Google and does not replace one.

It never marks a rule as passing without evidence. A scan older than 14 days, missing permissions or regions, a read cut short, resources without a price, the findings cap of the plan or rules the last scan did not evaluate (after an upgrade, for example) leave rules “not read”, and the screen and the PDF say why. Accepted risks and dismissed findings do not count as findings.

The tab is on every plan. The security and reliability pillars count rules when the account has the risk and compliance add-on; without it, the tab counts cost and, on Pro and Business, performance, and shows what the platform adds. The /v1 API and the MCP are on the Pro and Business plans.

How it counts

Counts, not a score

The review counts rules, not resources, and never sums a pillar up as a percentage: a score would suggest everything was looked at.

Three states per rule

Each rule of the pillar is in one of these three states, with posture and cost kept apart.

  • PassIt was fully evaluated in the last scan and has no open findings.
  • With findingsIt has at least one open finding. From the tab you go to its findings.
  • Not readIt could not be read or was read only in part, so it cannot be called passing.

Accepted risks and dismissed findings do not count as findings, but the rule still counts.

Never green without evidence

To show as passing, a rule has to clear at least these checks. If one fails, it stays “not read”, and the tab and the PDF explain why some rules are not read.

  1. The last scan is 14 days old or less
  2. No permissions or regions are missing
  3. There is a scan and reading its findings did not fail or stop short
  4. Resources have a price and the data needed to decide
  5. The findings cap of the plan was not reached
  6. The last scan already evaluated the rule: it was not added or turned on later

Clears all: counts as passing

Fails one: stays “not read”

To hand over

As a PDF, through the API and in your AI assistant

The same review outside the console: to send to whoever asks for it or to bring into your own tools.

Plans

What each plan includes

What each plan includes
FeatureFreeProBusiness
Pillars tab on every accountIncludedIncludedIncluded
Review PDFIncludedIncludedIncluded
Cost rules per pillar (those of your plan)IncludedIncludedIncluded
Rightsizing rules in performanceNot includedIncludedIncluded
Security and backup and resilience rulesNot included With the add-on With the add-on
/v1 API and MCPNot includedIncludedIncluded
Architecture map notices under reliabilityNot includedIncludedIncluded

The risk and compliance add-on is bought per account on Pro and Business. Without it, the security and reliability pillars show what the platform adds, with no rule counts.

Frequently asked questions