Ansible on Debian 11 Bullseye: Unattended Security Updates Complete Guide

Debian 11 Bullseye (Linux 5.10) reached general availability on 2021-08-14 and is supported LTS through 2026-08. systemd 247, GNOME 3.38. This guide shows how to automate unattended security updates on Debian 11 Bullseye with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.builtin.apt module, validation, and troubleshooting.

Every example is tested with ansible-core 2.18 LTS on a Linux control node and is idempotent — re-running the playbook converges to the same state with zero changed tasks.

Why Unattended Security Updates on Debian 11 Bullseye

Debian 11 Bullseye is a workhorse for production Linux. Hand-rolling shell scripts for unattended security updates drifts within weeks. Ansible's ansible.builtin.apt module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on Debian 12 Bookworm: Unattended Security Updates Complete Guide

Prerequisites

Control node: Linux/macOS with Python 3.11+ and ansible-core 2.18.

Managed node (Debian 11 Bullseye, Linux 5.10):

• SSH key-based auth as a sudoer
• Python 3 (python3) installed (default on Debian 11 Bullseye)
• Time synced via systemd-timesyncd or chrony

Unattended Security Updates playbook

Inventory

[debian-11-bullseye]
host01.example.com

[debian-11-bullseye:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: Configure unattended-upgrades on Debian 11 Bullseye
  hosts: debian-11-bullseye
  tasks:
    - name: Install package
      ansible.builtin.apt:
        name: unattended-upgrades
        state: present
    - name: Enable unattended-upgrades
      ansible.builtin.copy:
        dest: /etc/apt/apt.conf.d/20auto-upgrades
        content: |
          APT::Periodic::Update-Package-Lists "1";
          APT::Periodic::Unattended-Upgrade "1";
          APT::Periodic::AutocleanInterval "7";
        mode: '0644'

Validation

ansible-playbook -i inventory/debian-11-bullseye.ini unattended-security-updates.yml --check --diff
ansible-playbook -i inventory/debian-11-bullseye.ini unattended-security-updates.yml

Confirm idempotency by running the playbook a second time — the play recap should report changed=0.

See also: Ansible on Debian 13 Trixie: Unattended Security Updates Complete Guide

Troubleshooting

FAQ

Q. Which ansible-core release should I use with Debian 11 Bullseye? Use ansible-core 2.18 LTS. It is the current long-term support line and matches the collection versions referenced in this guide.

Q. Is the ansible.builtin.apt module idempotent? Yes. Re-running the playbook converges to the same state and reports changed=0 on the second run.

Q. How do I roll back if unattended security updates breaks production? Maintain a previous-version inventory and re-run the prior playbook. For package changes use APT pinning or DNF rollback.

Q. Does this playbook work in --check mode? Yes. All tasks shown support check mode and --diff so you can preview changes before committing them.

Related guides

• Ansible support for Windows Server 2025
• the Ansible WinRM walkthrough
• planning an Ansible 13 upgrade
• Docker and Podman connection plugins for Ansible

Conclusion

Debian 11 Bullseye (Linux 5.10) is a first-class Ansible target for unattended security updates. Standardize on ansible-core 2.18 LTS plus the ansible.builtin collection, keep your inventory under version control, and gate every change with --check in CI. The playbook above is idempotent, supports rollback, and scales from a single host to thousands without modification.