How does Ansible handle privilege escalation with become?

When a task or play sets become: true, Ansible connects to the managed node with the normal login user first, then invokes the configured become_method (most commonly sudo) to re-execute the module as the target user, usually root, only for that specific task.

- hosts: dbservers
  become: true
  become_method: sudo
  become_user: root
  vars:
    ansible_become_password: "{{ vault_sudo_pass }}"

Credentials for privilege escalation (a sudo password, if required) can be supplied via --ask-become-pass interactively, a vault-encrypted variable, or configured passwordless sudo on the target hosts, which is the most common production setup since it avoids needing to store or prompt for a second password at all. Because become is scoped per task or play rather than for the whole SSH session, a playbook can run most tasks as an unprivileged user and only escalate for the specific steps that genuinely need elevated permissions, limiting the blast radius of any single task going wrong.

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.

Webull! Receive free stock by signing up using the link: Webull signup.