AWS Infrastructure Health Assessment

Review the operational controls that influence security, recoverability, reliability, visibility, and AWS cost.

11 operational controlsAbout 4 minutesNo credentials or email
Assessment progress0 of 11
1. How are production data and critical configurations backed up?Backup
2. When was the last successful restore or recovery test?Backup
3. How is privileged AWS access controlled?Security
4. Are internet exposure and security-group rules reviewed against actual application needs?Security
5. How are operating-system, runtime, container, and dependency updates handled?Security
6. Can the team detect and respond to availability, capacity, and application failures?Observability
7. Are operational and audit logs centralized, retained, and usable during investigation?Observability
8. Does the architecture avoid known single points of failure for the required service level?Reliability
9. Are recovery-time and recovery-point expectations documented and matched by the design?Reliability
10. How are AWS spend, idle resources, commitments, and anomalies reviewed?Cost
11. Are change approval, incident ownership, escalation, and infrastructure handover documented?Operations

What the Health Report Reviews

The assessment covers operational evidence across backup, access, exposure, patching, observability, resilience, recovery, cost control, and ownership.

Risk-based priorities

Critical recovery and access gaps are separated from routine optimization work.

Operational breadth

Security is considered alongside monitoring, reliability, cost, and ownership.

Portable output

Download or print the priorities for internal review and planning.