It appears there is a `systemd-oom` user on the AWS AMI's which maps to the non-extant `systemd-oomd` package. Not sure what's putting it there, I presume at some point something installs `systemd-oomd` and yanks it before freezing the image.