Reports are where CloudEval shifts from infrastructure inspection to decision support.
For the public-safe count of checks and signals behind report outputs, see Evaluation coverage.
Priority decisions
The first review pass should start with the issues that have the clearest severity, confidence, business impact, ROI, or effort signal.
Breakdown views
Use report breakdowns when a summary number is not enough. Change the mode, path, and filters to compare issues by project, pillar, category, severity, or resource type.
Cost reports
Cost reports are designed to answer questions like:
- What does this project cost now?
- Where are the largest spending concentrations?
- Which opportunities are worth reviewing first?
Cost reports include region and currency inputs, monthly and annual context, and opportunity summaries.
Architecture reports
Architecture reports are designed to answer questions like:
- How healthy is this design overall?
- Which Well-Architected pillars need attention?
- Where are the critical and high-severity issues?
Architecture reports include:
- overall score
- pillar scores
- top critical issues
- high issue counts
How reports relate to projects
Reports are generated from projects, not from raw files in isolation. That matters because CloudEval can attach the latest snapshots, history, and share state back to the same project over time.
When to run both
Run both report types when you want a rounded view of tradeoffs. Architecture tells you about quality and risk. Cost tells you what the environment is likely to cost and where the biggest optimization levers are.
Next step
Use Run your first reports to generate output now, or move to Review cost and architecture findings for a practical review loop. Last modified on June 22, 2026
