Diagnosing a Production-Like Resource Incident on AWS EC2 Ubuntu Server

The idea Instead of just reading about high CPU or memory usage, I wanted to recreate the scenario myself: spike the resources, watch the system struggle, find the offending process, kill it, and conf