Connect As Who You Really Are

Remove a hardcoded remote_user and blanket sudo escalation these hosts cannot provide.

A intermediate Ansible challenge worth 10 points. Solve it hands-on in a real Ansible environment in your browser - no local setup, no fake shells.

The Challenge

Scenario: A play copied from an old cloud project hardcodes remote_user: deploy and become: true with sudo. On this estate every host is reached AS its own service account and there is no sudo at all, so the play fails on every host before doing any work.

Connect as the account the inventory already defines, drop the escalation, and have every production host write ~/etc/ownership-proof.txt proving which account really ran the tasks. Then run check.