Find AWS risk, cost waste and operational gaps across the six pillars

Do you have documented operational procedures for your AWS workloads?

Are deployments automated and repeatable?

Do teams review incidents and apply lessons learned?

Are workload metrics monitored against business outcomes?

Is operational ownership clear across teams?

Is identity and access managed using least privilege?

Are accounts, workloads, and data protected with consistent security controls?

Is security logging enabled and actively reviewed?

Are vulnerabilities identified and remediated on a defined cadence?

Are compliance obligations mapped to technical controls?

Are recovery objectives defined and tested?

Are workloads designed to tolerate component failure?

Are backups automated and regularly validated?

Is capacity monitored against current and future demand?

Are incident response and escalation paths tested?

Are services selected based on workload requirements rather than defaults?

Is performance monitored across user, application, and infrastructure layers?

Are resources rightsized and reviewed regularly?

Are architecture choices revisited as AWS services evolve?

Are performance issues linked back to business impact?

Do teams understand which workloads drive the largest AWS costs?

Are unused or underused resources identified regularly?

Are purchasing options reviewed, such as Savings Plans or Reserved Instances?

Are budgets, alerts, and ownership tags consistently used?

Are architecture decisions evaluated for cost impact?

Are workloads designed to reduce unnecessary resource consumption?

Are environments shut down or scaled down when not required?

Is data lifecycle management used to reduce storage waste?

Are sustainability considerations included in architecture reviews?

Are teams tracking efficiency improvements over time?