Ansible on Amazon Linux 2023: systemd Unit Authoring Complete Guide

Amazon Linux 2023 (Linux 6.1) reached general availability on 2023-03-15 and is supported 2028-03-15. dnf, deterministic LTS, optimized for EC2. This guide shows how to automate systemd unit authoring on Amazon Linux 2023 with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.builtin.systemd_service 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 systemd Unit Authoring on Amazon Linux 2023

Amazon Linux 2023 is a workhorse for production Linux. Hand-rolling shell scripts for systemd unit authoring drifts within weeks. Ansible's ansible.builtin.systemd_service module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on Alpine Linux 3.20: systemd Unit Authoring Complete Guide

Prerequisites

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

Managed node (Amazon Linux 2023, Linux 6.1): • SSH key-based auth as a sudoer • Python 3 (python3) installed (default on Amazon Linux 2023) • Time synced via systemd-timesyncd or chrony

systemd Unit Authoring playbook

Inventory

[amazon-linux-2023]
host01.example.com
[amazon-linux-2023:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: systemd unit authoring on Amazon Linux 2023
  hosts: amazon-linux-2023
  tasks:
    - name: App service unit
      ansible.builtin.copy:
        dest: /etc/systemd/system/app.service
        mode: '0644'
        content: |
          [Unit]
          Description=App
          After=network-online.target
          Wants=network-online.target
          [Service]
          Type=simple
          ExecStart=/usr/local/bin/app
          Restart=on-failure
          NoNewPrivileges=yes
          ProtectSystem=strict
          [Install]
          WantedBy=multi-user.target
    - name: App daily timer
      ansible.builtin.copy:
        dest: /etc/systemd/system/app.timer
        mode: '0644'
        content: |
          [Unit]
          Description=Daily app
          [Timer]
          OnCalendar=daily
          Persistent=true
          [Install]
          WantedBy=timers.target
    - name: Enable + start
      ansible.builtin.systemd_service:
        name: app.timer
        enabled: true
        state: started
        daemon_reload: true

See also: Ansible on Arch Linux: systemd Unit Authoring Complete Guide

Validation

ansible-playbook -i inventory/amazon-linux-2023.ini systemd-unit-authoring.yml --check --diff
ansible-playbook -i inventory/amazon-linux-2023.ini systemd-unit-authoring.yml

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

Troubleshooting

| Symptom | Likely cause | Fix | |---|---|---| | Could not resolve hostname | DNS / /etc/hosts mismatch | Add A record or fix /etc/hosts | | Sudo: a password is required | NOPASSWD missing | Grant ansible ALL=(ALL) NOPASSWD: ALL in /etc/sudoers.d/ansible | | Failed to lock /var/lib/dpkg/ | unattended-upgrades running | Wait or run systemctl stop unattended-upgrades |

See also: Ansible on Amazon Linux 2023: Container Engine Setup Complete Guide

FAQ

Q. Which ansible-core release should I use with Amazon Linux 2023? 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.systemd_service 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 systemd unit authoring 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

• the Windows Server 2025 + Ansible walkthrough • Ansible PowerShell automation via WinRM • ansible-core 2.20 deprecations • Ansible connection types: SSH, WinRM, Local, Docker, Network guide

Conclusion

Amazon Linux 2023 (Linux 6.1) is a first-class Ansible target for systemd unit authoring. 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.