How do I fix "Failed to start ntpd.service: Unit ntpd.service not found."?

Use chrony instead: `sudo dnf install -y chrony && sudo systemctl enable --now chronyd`. Migrate any custom `/etc/ntp.conf` settings to `/etc/chrony.conf`. Update cloud-init / Ansible / Packer steps that referenced ntpd. Verify with `chronyc sources`. Source: https://docs.aws.amazon.com/linux/al2023/ug/compare-with-al2.html

Amazon Linux 2023

Failed to start ntpd.service: Unit ntpd.service not found.

Failed to start ntpd.service: Unit ntpd.service not found.

What it means

Amazon Linux 2023 uses chrony for time sync; the ntpd service no longer exists.

Why it happens

Amazon Linux 2 used ntpd; AL2023 standardizes on chrony (chronyd). user-data or config management that enables/starts ntpd fails on AL2023.

How to fix it

Use chrony instead: `sudo dnf install -y chrony && sudo systemctl enable --now chronyd`.
Migrate any custom `/etc/ntp.conf` settings to `/etc/chrony.conf`.
Update cloud-init / Ansible / Packer steps that referenced ntpd.
Verify with `chronyc sources`.

Related deadline: Amazon Linux 2 EOL — 2026-06-30.

Find every instance in your project

The free EOLkits scanner runs in your browser (nothing uploaded) and flags this and related breakages across your IaC and dependency files.

Primary source: https://docs.aws.amazon.com/linux/al2023/ug/compare-with-al2.html

Get the full migration audit — $299, hash-anchored PDF →