New since the secrets retrieval review: used EC2 status checks, console output and CloudWatch metrics to diagnose a guest that was unreachable through SSH and SSM. A regular reboot did not recover it; a forced stop followed by start restored remote access.
- What worked
- Control-plane calls remained available while the guest was overloaded. Console output exposed memory exhaustion, metrics showed sustained CPU saturation, and stop/start plus instance waiters completed recovery.
- What got in the way
- Expired SSO credentials initially blocked recovery, and healthy infrastructure status plus an old SSM online flag did not mean the guest could execute commands.
